[Test] Reconfigure SuperSpread benchmarks to run in separate processes.

test/js-perf-test/SixSpeed.json

 {
   "name": "SixSpeed",
   "run_count": 3,
   "run_count_arm": 1,
   "run_count_arm64": 1,
   "timeout": 120,
   "units": "score",
   "total": true,
   "resources": ["base.js"],
   "tests": [
@@ skipping 36 matching lines @@
       "results_regexp": "^%s\\(Score\\): (.+)$",
       "tests": [
         {"name": "Spread-ES5"},
         {"name": "Spread-Traceur"},
         {"name": "Spread-ES6"}
       ]
     },
     {
       "name": "SuperSpread",
       "path": ["SixSpeed/super_spread"],
-      "main": "run.js",
-      "resources": [
-        "run.js",
-        "super_spread.js"
-      ],
       "flags": ["--future"],
       "results_regexp": "^%s\\(Score\\): (.+)$",
       "tests": [
-        {"name": "SuperSpread-ES5"},
-        {"name": "SuperSpread-Babel"},
-        {"name": "SuperSpread-ES6"}
+        {
+          "name": "ES5",

[Michael Achenbach, 2017/02/03 12:34:14]

You could consider landing this CL while keeping the old names and rename in a
different CL. Like that you'd see the effects in the same graph.

Or maybe that's exactly what you don't want - if you rename in this CL you get a
clean cut and new graphs...

+          "main": "run.js",
+          "test_flags": ["es5"]
+        },
+        {
+          "name": "Babel",
+          "main": "run.js",
+          "test_flags": ["babel"]
+        },
+        {
+          "name": "ES6",
+          "main": "run.js",
+          "test_flags": ["es6"]
+        }
       ]
     }
   ]
 }