module: have a single hooks thread for all workers

[dygabo]

This implements reusing the single esm loader hooks thread for all the subsequent workers.
It started as a trial to solve the test contributed by @GeoffreyBooth from #50752. The test content is taken over from that branch and only slightly modified to also support transitive worker threads (that are started by some worker and not by the main thread). This is probably a not very common use case but the interface supports it so I put in the test as well.

With this initial commit all tests are passing.

[==========] 157 tests from 28 test suites ran. (2328 ms total)
[  PASSED  ] 157 tests.
make -s jstest
ninja: Entering directory `out/Release'
ninja: no work to do.
[04:49|% 100|+ 4095|-   0]: Done

All tests passed.

Let's start a discussion and if there are additional usages that are missed by the implementation or if something needs improvements, let me know. If the implementation matches the expectations, we could close the test-only PR and continue the discussion here. Let me know your thoughts.

[nodejs-github-bot]

Review requested:

• @nodejs/loaders

[targos]

@nodejs/loaders

[GeoffreyBooth]

Great work!

[JakobJingleheimer]

Yahoo! 🙌 great work @dygabo. thank you for this!

a few nits, and a couple small tweaks requested.

[JakobJingleheimer]

🙌

[dygabo]

I added a testcase for a scenario where a worker thread import operation would call process.exit. I.e.

• the main thread imports some module that creates a Worker thread
• the Worker thread script imports a module => this gets delegated to the single hook thread
• on the hooks thread this causes a process.exit
• this process.exit now gets propagated to main thread and all workers.

I think this is a change in behavior compared to the previous version. Is this scenario covered correctly now? Is this an acceptable change in behavior?
If not, can this be covered with a follow-up or should it be covered here?