Including libyuv headers using fully qualified paths.

Using fully qualified paths to include libyuv headers allows WebRTC to
avoid to rely on the //third_party/libyuv:libyuv_config target to
set the -I compiler flag.

Today some WebRTC targets depend on //third_party/libyuv only to
include //third_party/libyuv:libyuv_config but with fully qualified
paths this should not be needed anymore.

A follow-up CL will remove //third_party/libyuv from some targets that
don't need it because they are not including libyuv headers.

Bug: webrtc:8605
Change-Id: Icec707ca761aaf2ea8088e7f7a05ddde0de2619a
No-Try: True
Reviewed-on: https://webrtc-review.googlesource.com/28220
Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org>
Reviewed-by: Magnus Flodman <mflodman@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#21209}
diff --git a/test/DEPS b/test/DEPS
index 39f107b..1cf56a8 100644
--- a/test/DEPS
+++ b/test/DEPS
@@ -17,6 +17,7 @@
   "+sdk",
   "+system_wrappers",
   "+voice_engine",
+  "+third_party/libyuv",
 ]
 
 specific_include_rules = {