Reproduce wrong line numbers in stack traces under Node v20

[gthb]

This reproduces the apparent bug (whether the root cause is in ts-node or in Node itself) that under Node v20.0.0 onwards (EDIT: and now also v18.19.0), line numbers are incorrect in stack traces thrown in TypeScript files, seeming to correspond to a module file stripped of its type declarations.

The CI runner failed to install Node v20 (when that was in run.sh, prior to b551e87).

Once I changed that to v18.19.0, the CI output still reports a bunch of cp: cannot remove '/usr/local/include/node/v8-locker.h': Permission denied, but it does seem to finish installing v18.19.0, and the CI output reports the problem I'm reproing (but also some Node internal error/warning):

Grr, stack seems to have wrong line numbers.
node:internal/process/esm_loader:40
      internalBinding('errors').triggerUncaughtException(
                                ^

Error: bar
    at foofn (file:///home/runner/work/ts-node-repros/ts-node-repros/example.ts:2:11)
    at file:///home/runner/work/ts-node-repros/ts-node-repros/example.ts:5:5
    at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:24)
    at async loadESM (node:internal/process/esm_loader:34:7)
    at async handleMainPromise (node:internal/modules/run_main:106:12)

Node.js v18.19.0
Process exited with code: 1

(The CI job still reports green, which is a little misleading, but maybe that's the convention in this repo?)

If you change the Node version to v18.8.2 or earlier, the test passes, i.e. the line number will be correct.