Rewrite "node:worker_thread" "Worker" creation

[bartlomieju]

Right now using Worker from node:worker_thread is racy as the setup data (environmentData, threadId and workerData) arrive in the first message (#22672).

We need to rewrite how we initialize these workers. Currently they are piggy-backing off of Web Worker but that is not really correct. @satyarohith, @mmastrac and I had an offline discussion about it and we decide to rewrite large chunks of worker_threads module.

Here's what we need to do:

1. Don't rely on Worker from 11_workers.js, instead use raw ops to create a worker instance in native code - this will lead to a bit of copy pasting of code, but that's fine for now. In essence we need to call op_create_worker there and have the code for Worker.#pollControl and Worker.#pollMessages() in ext/node/polyfills/worker_threads.ts.
2. Once point 1 is addressed we need to extend op_create_worker to be able to accept data for environmentData (that needs to apply structured clone algorithm) and workerData (also using structured clone algo). This data should be passed to bootstrap.workerRuntime in runtime/web_worker.rs and then piped to internals.node.initialize() and further to internals.__initWorkerThreads().
3. At this point we should be able to remove the racy message received from the host that sets up all the necessary data and proceed with further refactors.

EDIT: I was able to clean up this bit before addressing previous points (#22785)

4. Once we're able to do that we should proceed to rewrite how isMainThread is handled in node:worker_threads - this is something that should be passed explicitly instead of relying on quirky PRIVATE_WORKER_THREAD_NAME.
5. When we fix isMainThread we need to remove PRIVATE_WORKER_THREAD_NAME in favor of passing the name from option bag of worker_threads::Worker properly.