Move the kernel isolate snapshot out of the 'runtime' target to reduce build times on the simulator…

BUILD.gn

Index: BUILD.gn
diff --git a/BUILD.gn b/BUILD.gn
index bc5f84f07aef9d10ab8e47c4c5be630850efa00d..45c408ffaaa1a056480b4baaec188e1a62d16afb 100644
--- a/BUILD.gn
+++ b/BUILD.gn
@@ -42,6 +42,12 @@ group("runtime") {
     "runtime/bin:sample_extension",
     "runtime/bin:test_extension",
     "runtime/vm:patched_sdk",
+  ]
+}
+
+group("runtime_kernel") {
+  deps = [
+    ":runtime",

[jamesr1, 2017/01/31 23:10:02]

unfortunately this breaks the fuchsia GN build as this non-testonly target now
depends on a target marked testonly in fuchsia, see line 35.  Why does
//dart:runtime depend on run_vm_tests?  Is that not actually a test-only target
or should //dart:runtime (and thus //dart:runtime_kernel) be considered testonly
as well?

[rmacnak, 2017/01/31 23:26:10]

runtime and runtime_kernel should have the same testonly-ness.

I believe the grouping of run_vm_tests under runtime is mostly historical: we
did it that way in GYP, our bots build the "runtime" target and we're keeping GN
and GYP roughly in sync until we can stop supporting GN. This probably should be
refactored after that.

 
     # TODO(rmacnak): Link this into 'dart'
     "utils/kernel-service:kernel-service",