test: parallelize test-without-async-context-frame correctly

It previously re-einvented the pattern matching that's already
supported by test.py, and was running the tests one by one,
which can lead to time out on slower machines.
This move it to sequential and use wildcard
support in test.py to correctly parallelize the tests.

PR-URL: #60273
Fixes: #60268
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Chemi Atlow <chemi@atlow.co.il>

Author: joyeecheung

test/parallel/test-without-async-context-frame.mjs

@@ -0,0 +1,24 @@
+import { isWindows } from '../common/index.mjs';
+import { spawn } from 'node:child_process';
+import { once } from 'node:events';
+import { fileURLToPath } from 'node:url';
+import { strictEqual } from 'node:assert';
+
+const python = process.env.PYTHON || (isWindows ? 'python' : 'python3');
+
+const testRunner = fileURLToPath(
+  new URL('../../tools/test.py', import.meta.url)
+);
+
+const proc = spawn(python, [
+  testRunner,
+  `--mode=${process.features.debug ? 'debug' : 'release'}`,
+  `--shell=${process.execPath}`,
+  '--node-args=--no-async-context-frame',
+  '*/test-async-local-storage-*',
+], {
+  stdio: ['inherit', 'inherit', 'inherit'],
+});
+
+const [code] = await once(proc, 'exit');
+strictEqual(code, 0);