repl: use inspector over vm

[avivkeller]

This PR switches the REPL from node:vm to node:inspector, moving it from a synchronous to an asynchronous evaluator. This brings the following improvements:

1. Top-level await is now natively supported by the inspector, so --no-experimental-repl-await is no longer accepted. This also resolves a known limitation where TLA would invalidate the lexical scoping of const declarations.
2. Static imports such as import ... from '...' are now transformed into real dynamic imports and executed, rather than throwing Cannot use import statement outside a module with a hint to rewrite the import manually. This isn't strictly required by removing node:vm, but the change makes it easier. I can split this into a separate PR if preferred.
3. Several node:vm issues are resolved (see the list below), and users can now attach process listeners without breaking the REPL.
4. Errors are more detailed: for example, showing the specific line in a .load-ed file where an error was thrown.

---

This is a semver-major change; see the reasons listed in the notable changes section.

---

Removed Tests

• addons/repl-domain-abort, parallel/test-repl-domain.js: We no longer rely on the domain module, so testing it is no longer needed.
  • parallel/test-repl-no-terminal-restore-process-listeners.js: An extension of the above — we no longer modify the ability to set process listeners.
  • parallel/test-repl-uncaught-exception-async.js / parallel/test-repl-uncaught-exception.js / parallel/test-repl-tab-complete-nested-repls.js: An extension of the above; this test case no longer throws an error.
• known_issues/test-repl-require-context.js: This known issue has been resolved.
• parallel/test-repl-top-level-await.js: No need to test TLA — it's supported natively by the inspector.
  • parallel/test-repl-preprocess-top-level-await.js: An extension of the above; the REPL no longer pre-processes top-level await.
• parallel/test-repl-preview-without-inspector.js: The REPL no longer works without the inspector.
• parallel/test-util-sigint-watchdog.js: This tested code that has been removed as part of this migration.
• pseudo-tty/repl-dumb-tty.js: There's currently no way to conditionally run these tests (run only when inspector is available).

---

Fixes: #61390
Fixes: #63126
Fixes: #38503
Fixes: #39387 (Closes #39392)
Fixes: #37445
Fixes: #38145
Fixes: #33369
Fixes: #48131
Fixes: #8309
Fixes: #39689
Fixes: #18931

---

Notable Change

The REPL has been re-implemented on top of the V8 Inspector (node:inspector) rather than node:vm. This moves the REPL from a synchronous to an asynchronous evaluator and resolves long-standing design quirks that stemmed from the vm-based design:

• Because the inspector natively supports top-level await, the --no-experimental-repl-await flag is no longer accepted, and top-level await no longer corrupts the lexical scoping of const/let declarations. Additionally, statements that would normally return a Promise are now awaited until they settle.
• Lines such as import { readFile } from 'node:fs/promises' are now transformed into real dynamic imports and executed.
• _ and _error are available even in REPLs with a modified context.
• Users can now add listeners (e.g. uncaughtException) without disrupting evaluation.
• Throwing inside queueMicrotask/timer callbacks, and vm async timeouts, no longer take down the process.
• Certain side-effect free Proxy's, Getters, and other non-static properties can be tab/auto-completed.
• And more

Breaking changes

In addition to the removal of --no-experimental-repl-await and similar await changes noted above:

• Because errors now surface through the inspector, their output (including the added detail) can differ from previous releases. Code or tests that match on exact REPL error or stack-trace text may need to be updated.
• The caret/offset indicator that pointed at the precise location of a SyntaxError is no longer emitted in the main REPL; this information is still available programmatically in the stack trace.
• V8's Inspector does not carry RegExp matches over to the global object across multiple evaluations.

[nodejs-github-bot]

Review requested:

• @nodejs/config

[avivkeller]

cc @nodejs/repl @nodejs/inspector

[github-actions]

The notable-change PRs with changes that should be highlighted in changelogs. label has been added by @avivkeller.

Please suggest a text for the release notes if you'd like to include a more detailed summary, then proceed to update the PR description with the text or a link to the notable change suggested text comment. Otherwise, the commit will be placed in the Other Notable Changes section.

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[qwitwa]

Does this change make tab-completions side-effect free in all cases?
(I ended up here after clicking through completion side-effect issues)
I see regex and generator side effects in the linked issues; my case was with dax's $ tag function, where

await $`echo hello`.sometext

was printing hello whilst tab completing.

[avivkeller]

Hi @qwitwa! Unfortunately, that specific case is not resolved by this PR. Although, that might be an issue with V8, since the REPL relies on CDP's throwOnSideEffect, which determines $ as side-effect free (even though, apparently, it's not)

[avivkeller]

Bump @nodejs/repl @nodejs/vm @nodejs/inspector

[avivkeller]

@qwitwa I've re-written the completion logic to benefit from the same inspector changes as the rest of this PR, including better side effect detection. I believe the issue stemmed from the fact that our completion was not relying fully on CDP's side effect detection, and instead some custom side effect detection logic in cases of unique objects (e.g. getters, proxies).

The latest changes to this PR should resolve your issue, and allow for completions in more side-effect free cases.