chore(ci): reorganize e2e/perf test running

Now, running protractor configs by default only runs e2e tests. If
the --benchmark flag is added, it runs only the perf tests, and always
restarts the browser in between tests. If the --dryrun test is added,
the perf tests are run only once.

This should make it easier to run perf tests versus example e2e tests,
and help stabilize the travis build because perf tests always
run with a clean browser.

scripts/ci/test_e2e_dart.sh

@@ -21,3 +21,4 @@ trap killServer EXIT
 sleep 10
 
 ./node_modules/.bin/protractor protractor-dart2js.conf.js --browsers=${E2E_BROWSERS:-Dartium}
+./node_modules/.bin/protractor protractor-dart2js.conf.js --benchmark --dryrun --browsers=${E2E_BROWSERS:-Dartium}

scripts/ci/test_e2e_js.sh

@@ -27,3 +27,4 @@ if [[ -n "$E2E_BROWSERS" ]]; then
 fi
 
 ./node_modules/.bin/protractor protractor-js.conf.js $OPTIONS
+./node_modules/.bin/protractor protractor-js.conf.js $OPTIONS --benchmark --dryrun

scripts/ci/test_perf.sh

@@ -22,4 +22,4 @@ trap killServer EXIT
 sleep 10
 
 ./node_modules/.bin/protractor protractor-js.conf.js --browsers=$PERF_BROWSERS --benchmark
-./node_modules/.bin/protractor protractor-dart2js.conf.js --browsers=$PERF_BROWSERS --benchmark
+./node_modules/.bin/protractor protractor-dart2js.conf.js --browsers=$PERF_BROWSERS --benchmark