modules: implement deferred import for dynamic modules

[MayaLekova]

modules: implement deferred import for dynamic modules

This PR adds support for deferring the import of modules in additional
cases, such as importing a dynamic module. It also adds a test for
this case.

Refs: https://github.com/tc39/proposal-defer-import-eval
Signed-off-by: Maya Lekova maya@igalia.com

[nodejs-github-bot]

Review requested:

• @nodejs/loaders
• @nodejs/security-wg
• @nodejs/startup
• @nodejs/typescript
• @nodejs/vm

[MayaLekova]

I tried fixing the cctest failures, but apparently the change to ModuleWrap::Evaluate signature also changed the behaviour of the VM module. Still experiencing this error:

(node:50255) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
node:internal/vm/module:215
      validateObject(options, 'options');
      ^

TypeError [ERR_INVALID_ARG_TYPE]: The "options" argument must be of type object. Received type number (-1)
    at SourceTextModule.evaluate (node:internal/vm/module:215:7)
    at /home/maya/Work/node/out/Release/cctest:1:328
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5) {
  code: 'ERR_INVALID_ARG_TYPE'
}

@joyeecheung just FYI, I'll keep trying to fix it.

[joyeecheung]

This is the public API for the vm API, which is not used by the built-in loader at all, and it's not the same as the module wrap's evaluate, which is internal and used by both. There's no need to touch this.

[joyeecheung]

Can you drop the amaro update commit? I don't think that's supposed to be in this PR?