lib: add internal/primordials_staging module

[LiviaMedeiros]

We have quite a few builtins that can not be included in primordials, usually because their existence is conditional (either they require experimental flag, or they can be disabled with --no- flag).
We have to retrieve such builtins from globalThis, which is exposed to userland and is mutable by design.
Additionally, in some modules that are part of early bootstrap we can not do top-level assignment synchronously, because the builtins are not defined yet. Because of that, we have to get them on demand from userland, making them extremely prone to prior mutation.

This PR adds internal/primordials_staging module which is populated on pre-execution stage (late enough to have them on global, and early enough to not be affected by userland code), and allows lazy loading of experimental builtins without relying on globalThis in runtime.

The name is subject to bikeshedding. I chose staging since objects in this module are expected to be included in primordials at some point in the future.

Some related PRs:

• buffer: add Buffer.fromHex() and Buffer.fromBase64() #61157 - would benefit from this, otherwise it has to lazy load mutable/polyfillable methods in runtime.
• fs: add Temporal.Instant support to Stats and BigIntStats #60789 - would be hardened by this, otherwise it might lazyload polyfilled/mutated Temporal.
• lib: add internal Temporal utils #63312 - proposes primordial-ish access to Temporal, this is broader-scoped alternative to that part.

TODO:

• add docs
• add test
• adjust linter suggestions

cc @nodejs/startup @Renegade334

[nodejs-github-bot]

Review requested:

• @nodejs/loaders
• @nodejs/startup

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.06%. Comparing base (4ee7567) to head (54db761).
⚠️ Report is 23 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #63464      +/-   ##
==========================================
+ Coverage   90.05%   90.06%   +0.01%     
==========================================
  Files         714      715       +1     
  Lines      225876   226009     +133     
  Branches    42737    42749      +12     
==========================================
+ Hits       203408   203562     +154     
+ Misses      14244    14234      -10     
+ Partials     8224     8213      -11     

Files with missing lines	Coverage Δ
lib/internal/freeze_intrinsics.js	96.96% <100.00%> (-0.01%)	⬇️
lib/internal/fs/utils.js	98.43% <100.00%> (ø)
lib/internal/modules/esm/translators.js	97.51% <100.00%> (ø)
lib/internal/primordials_staging.js	100.00% <100.00%> (ø)
lib/internal/process/pre_execution.js	98.51% <100.00%> (+0.12%)	⬆️
lib/internal/util.js	96.63% <100.00%> (-0.20%)	⬇️
lib/internal/util/comparisons.js	99.71% <100.00%> (+<0.01%)	⬆️
lib/v8.js	98.77% <100.00%> (ø)

... and 26 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nodejs-github-bot]

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

[Renegade334]

freeze_intrinsics also runs in pre-execution, so this wouldn't be necessary.

[LiviaMedeiros]

Agreed. Still, i'd prefer it to stay for consistency, so it doesn't differ from linter suggestion and the internals never take builtins from globalThis directly.
Unless there is another reason to keep globalThis here.

[Renegade334]

This is only capturing the global object properties, not the object tree, so eg. Temporal.Instant.fromEpochNanoseconds(), new WebAssembly.Module() are still user-mutable.