src: use NativeModuleLoader to compile all the bootstrappers

[joyeecheung]

This patch moves all the bootstrapper compilation to use
NativeModuleLoader::CompileAndCall(). With this we no longer
need to mess with the error decoration and handling any more -
there is no point in handling the JS error occurred during bootstrapping
by ourselves, we should just crash or let the VM handle it.

Checklist

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

[nodejs-github-bot]

@joyeecheung build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1768/pipeline

[joyeecheung]

cc @addaleax @jasnell @devsnek

Since the top-level indentation in the two bootstrappers are now eliminated, this patch would be easier to review with https://github.com/nodejs/node/pull/24775/files?w=1 (with the whitespace-only changes stripped)

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

[joyeecheung]

Resume: https://ci.nodejs.org/job/node-test-pull-request/19134/ ✔️

[joyeecheung]

@addaleax @jasnell @devsnek @nodejs/process Can I have some reviews please? Thanks!

[joyeecheung]

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

[joyeecheung]

Landed in edcb950, thanks!

[BridgeAR]

This does not land cleanly on v11.x (it seems like it relies on the console changes which did not land cleanly and it is likely that they apply fine as soon as they got backported). Please open a backport or change the label accordingly.

[BridgeAR]

This does not land cleanly or near cleanly even after applying the recent console commits :/.

@joyeecheung could you please have another look? There are a couple of PRs from you which still need backports but I do not know which is the first one to backport and if there's maybe a semver-major PR which should be backported without breaking changes similar to the console one.

[joyeecheung]

@BridgeAR I think this does not apply cleanly mostly because there are out-of-order commits backported to v11.x-staging before this one is backported. I'll try reverting those first before doing a clean backport

[joyeecheung]

This could land cleanlier on v11.x-staging after

1. Reverting these out-of-order commits first, in this order

e97acf7 lib: expose all type checks from the internal types module
c168672 inspector: move process.binding to internalBinding
617bfe4 lib: remove internalBinding('config').pendingDeprecation
55d185f os: move process.binding('os') to internalBinding
0cde1a4 lib: remove unused NativeModule/NativeModule wraps
88a5449 src,lib: make process.binding('config') internal
1ec4f8d lib: remove duplicated noop function

2. Cherry-pick fs: make process.binding('fs') internal #22478

There will still be a small conflict in src/node.cc which I suspect is caused by the out-of-order cherry-pick of 56b2a7274c inspector: split the HostPort being used and the one parsed from CLI but simply reverting that could trigger some other bigger conflicts.