repl: use vm DONT_CONTEXTIFY context

[legendecas]

REPL does not need interception behavior in the vm context. Creating
a DONT_CONTEXTIFY context to reduce the chance to be impacted by V8
interceptor API changes.

No observable behavior or tests should break. This does not fix the
behavior in vm with the V8 upgrade, only REPL is fixed.

Refs: #61898 (comment)

[codecov]

Codecov Report

❌ Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 89.70%. Comparing base (7547e79) to head (32d1f5a).

Files with missing lines	Patch %	Lines
lib/repl.js	50.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #62371      +/-   ##
==========================================
- Coverage   91.60%   89.70%   -1.90%     
==========================================
  Files         337      676     +339     
  Lines      140745   206693   +65948     
  Branches    21802    39582   +17780     
==========================================
+ Hits       128925   185421   +56496     
- Misses      11595    13424    +1829     
- Partials      225     7848    +7623     

Files with missing lines	Coverage Δ
lib/repl.js	94.01% <50.00%> (+1.12%)	⬆️

... and 459 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.

[Renegade334]

For any usage case involving spinning up multiple concurrent node:repl instances, this would presumably be quite breaking? (No idea whether this is a common phenomenon.)