test: move test-worker-init-failure to sequential

[Trott]

(Includes the change in #34727 to avoid subsequent merge conflict. This supplants it.)

Unfortunately, the test is sensitive to resource constraints and is
unreliable on macOS in CI when in parallel.

Fixes: #34727

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

[Trott]

Stress test that will hopefully show the issue on master: https://ci.nodejs.org/job/node-stress-single-test/165/
Stress test that will hopefully show the issue fixed with this PR: https://ci.nodejs.org/job/node-stress-single-test/166/

[addaleax]

Do we know why the test is sensitive to resource constraints?

[Trott]

Do we know why the test is sensitive to resource constraints?

I'm guessing because it opens a lot of files (128).

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/32741/

[Trott]

Do we know why the test is sensitive to resource constraints?

I'm guessing because it opens a lot of files (128).

An alternative we could experiment with is halving all the hard-coded numbers.

[gireeshpunathil]

IMO the sensitivity to resource constraints is by de# the test, and it actually helped (and helps) to detect unforeseen control paths that are not covered in code and test, so is best placed to run in /parallel.