benchmark: add new tests for benchmarks and add new ENV

The env NODE_RUN_ALL_BENCH_TESTS was introduced
to enable benchmark tests to run all configs when it is passed.

Some tests that have file names different from the original benchmark
were using dashes in places that needed underscores and have been
renamed.

Some benchmarks that did not have tests were created. These are:

- test/benchmark/test-benchmark-abort_controller.js
- test/benchmark/test-benchmark-error.js
- test/benchmark/test-benchmark-https.js
- test/benchmark/test-benchmark-perf_hooks.js
- test/benchmark/test-benchmark-permission.js
- test/benchmark/test-benchmark-sqlite.js
- test/benchmark/test-benchmark-test_runner.js
- test/benchmark/test-benchmark-webstorage.js

Author: brunocroh

test/benchmark/test-benchmark-abort_controller.js

@@ -0,0 +1,10 @@
+'use strict';
+
+require('../common');
+
+// Minimal test for assert benchmarks. This makes sure the benchmarks aren't
+// completely broken but nothing more than that.
+
+const runBenchmark = require('../common/benchmark');
+
+runBenchmark('abort_controller');

…/benchmark/test-benchmark-async-hooks.js …/benchmark/test-benchmark-async_hooks.jstest/benchmark/test-benchmark-async-hooks.js renamed to test/benchmark/test-benchmark-async_hooks.js test/benchmark/test-benchmark-async-hooks.js renamed to test/benchmark/test-benchmark-async_hooks.js

@@ -0,0 +1,7 @@
+'use strict';
+
+require('../common');
+
+const runBenchmark = require('../common/benchmark');
+
+runBenchmark('error');

…enchmark/test-benchmark-child-process.js …enchmark/test-benchmark-child_process.jstest/benchmark/test-benchmark-child-process.js renamed to test/benchmark/test-benchmark-child_process.js test/benchmark/test-benchmark-child-process.js renamed to test/benchmark/test-benchmark-child_process.js

@@ -0,0 +1,14 @@
+'use strict';
+
+const common = require('../common');
+
+if (!common.enoughTestMem)
+  common.skip('Insufficient memory for HTTPS benchmark test');
+
+// Because the http benchmarks use hardcoded ports, this should be in sequential
+// rather than parallel to make sure it does not conflict with tests that choose
+// random available ports.
+
+const runBenchmark = require('../common/benchmark');
+
+runBenchmark('https');

test/benchmark/test-benchmark-error.js

@@ -0,0 +1,7 @@
+'use strict';
+
+require('../common');
+
+const runBenchmark = require('../common/benchmark');
+
+runBenchmark('perf_hooks');

test/benchmark/test-benchmark-https.js

@@ -0,0 +1,7 @@
+'use strict';
+
+require('../common');
+
+const runBenchmark = require('../common/benchmark');
+
+runBenchmark('permission');

test/benchmark/test-benchmark-perf_hooks.js

@@ -0,0 +1,7 @@
+'use strict';
+
+require('../common');
+
+const runBenchmark = require('../common/benchmark');
+
+runBenchmark('sqlite');

test/benchmark/test-benchmark-permission.js

@@ -0,0 +1,7 @@
+'use strict';
+
+require('../common');
+
+const runBenchmark = require('../common/benchmark');
+
+runBenchmark('test_runner')