Use built Chromium dependencies in run_gpu_test.

content/telemetry.isolate

Index: content/telemetry.isolate
diff --git a/content/telemetry.isolate b/content/telemetry.isolate
index 4679a5e8aae5c2116326d60be9634f9c2b41e6e5..7c73fb3a6befec579b83a069452dbb77357517c1 100644
--- a/content/telemetry.isolate
+++ b/content/telemetry.isolate
@@ -25,6 +25,8 @@
           '../third_party/flot/jquery.flot.min.js',
           '../third_party/webpagereplay/',
           '../tools/telemetry/',
+          # Chromium local path information for Telemetry's binary_manager.
+          '../tools/perf/core/binary_dependencies.json',

[Ken Russell (switch to Gerrit), 2015/09/23 17:42:17]

Should this be added here or in the isolates which depend on this one? Since
crash_service.exe is built at the chrome/ level and this isolate's in content/
there's a layering problem where this one can't directly include the built
executable, but this JSON file specifies that it might exist.

It's not a big problem either way but it would be nice if the base Telemetry
isolate could directly include all of its binary dependencies. Maybe we should
move it out of content/ and into chrome/.

[aiolos (Not reviewing), 2015/09/23 18:58:45]

This file is actually from https://codereview.chromium.org/1361523003/ and will
disappear after rebasing. I also moved the json file out of the
telemetry.isolate, and into it's own isolate which is currently in content.
Should I move it to chrome?

[Ken Russell (switch to Gerrit), 2015/09/23 19:19:02]

Yes, given that Telemetry has implicit dependencies on targets from chrome/, I
think this file should be moved back to chrome/. That probably implies
telemetry_gpu_unittests.isolate needs to be moved too.

           # For Telemetry's screenshot support.
           '<(PRODUCT_DIR)/bitmaptools<(EXECUTABLE_SUFFIX)',
         ],