repl: don't use deprecated domain module

[RedYetiDev]

This PR refactors the REPL module by eliminating the deprecated node:domain module. It replaces its functionality with a modern approach using a try/catch block and process.setUncaughtExceptionCaptureCallback.

Why?

The domain module has been deprecated for a while, and its use is discouraged. Despite this, Node.js still relies on it in a key component: the REPL. To lead by example and promote best practices, this PR updates the REPL module to use more up-to-date error-handling mechanisms, completely removing reliance on the deprecated domain module.

Additionally, this update simplifies the REPL's code and results in a slight performance improvement—though the gains are give-or-take a few ticks and may not be noticeable.

Breaking Changes

This PR is marked as semver-major PRs that contain breaking changes and should be released in the next major version. because it introduces functional changes to the REPL:

• Removal of options.domain: This undocumented feature is removed (without a formal deprecation cycle, given the domain module itself is deprecated, and the feature was never documented nor tested).
• Removal of ERR_INVALID_REPL_INPUT: This error is no longer needed, as after this change, there are no restricted inputs.

This PR is also marked needs-citgm PRs that need a CITGM CI run. in case any of the above cause breakages.

---

CC @nodejs/repl
CC @nodejs/tsc due to semver-major PRs that contain breaking changes and should be released in the next major version.

[codecov]

Codecov Report

Attention: Patch coverage is 95.89041% with 3 lines in your changes missing coverage. Please review.

Project coverage is 88.40%. Comparing base (fa8f149) to head (dcf5e94).
Report is 57 commits behind head on main.

Files with missing lines	Patch %	Lines
lib/repl.js	95.89%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #55204      +/-   ##
==========================================
- Coverage   88.41%   88.40%   -0.02%     
==========================================
  Files         652      653       +1     
  Lines      186918   187451     +533     
  Branches    36072    36082      +10     
==========================================
+ Hits       165270   165718     +448     
- Misses      14891    14965      +74     
- Partials     6757     6768      +11     

Files with missing lines	Coverage Δ
lib/internal/errors.js	96.99% <ø> (-0.01%)	⬇️
lib/repl.js	94.84% <95.89%> (-0.12%)	⬇️

... and 128 files with indirect coverage changes

[mcollina]

I have a rough feeling that you'd need to add
a FinalizationRegistry to clear up any instances

[RedYetiDev]

I have a rough feeling that you'd need to add a FinalizationRegistry to clear up any instances

Why? Is unsetting the callback on close() not enough?

[mcollina]

This is still leaking things in the process object, and domain is a much safer way to do so anyway.

[RedYetiDev]

and domain is a much safer way to do so anyway.

I disagree. This is different than the domain. The domain bypasses the listener and inserts a callback before these listeners can even be called. This merely adds a listener, and later removes it. How is that "leaking"? The attachment to the process object is controlled.