Roadmap for stabilization of vm modules

According to @SimenB, here are the issues that should probably be taken care of before we unflag and mark vm modules as stable:

• vm.Script's importModuleDynamically should get a reference to the context used to run it (#35714)
• https://github.com/nodejs/node/issues/43899
• https://github.com/nodejs/node/issues/31234
• VM ESM with dynamic imports resolves promises before linking is complete (#33216)
• https://github.com/nodejs/node/issues/60242
• https://github.com/nodejs/node/issues/35848
• https://github.com/nodejs/node/issues/31234
• https://github.com/nodejs/node/issues/31658
• SourceTextModule memory leak (#33439)
• Segmentation fault with import() instead of calling importModuleDynamically (#35889)
• importModuleDynamically for vm module is cached (#36351)
• https://github.com/nodejs/node/issues/50113
• https://github.com/nodejs/node/issues/59118
• https://github.com/nodejs/node/issues/59656
• https://github.com/nodejs/node/issues/43663
• Change API of module.lnk((specifier) => module) to module.link(specifiers, modules) so that it has fewer C++ -> JS calls and can be reused to implement require(esm).
• Source phase import support.

Tracking issue in Jest: https://github.com/jestjs/jest/issues/9430
/cc @devsnek

首先查看尚未勾选的关联 issue，尤其是 #35714、#43899、#31234、#33216、#60242 以及 source phase import 支持。https://github.com/jestjs/jest/issues/9430 上的 Jest 跟踪 issue 提供了更多背景信息。当剩余的稳定性阻碍都得到解决，并且可以移除 vm modules 的 flag、将其标记为 stable 时，即表示完成。