skipFiles does not suppress "uncaught" exceptions in web streams

### Version 22.4.1 ### Platform ```text Microsoft Windows NT 10.0.22635.0 x64 ``` ### Subsystem _No response_ ### What steps will reproduce the bug? Run this code in the VSCode debugger with `"skipFiles":["<node_internals>/**"]` in the launch configuration. ``` import net from 'node:net'; import stream from 'node:stream'; const socket = net.connect('http://host.invalid.'); socket.on('error', (e) => { console.error('Caught the error', e.message); }); let myStream = stream.Duplex.toWeb(socket); setTimeout(() => { console.log('done'); }, 1000); ``` ### How often does it reproduce? Is there a required condition? _No response_ ### What is the expected behavior? Why is that the expected behavior? It is expected that the debugger won't trip. This promise rejection is entirely created and handled within node's internals and should be suppressed by the VSCode's `skipFiles` filter. ### What do you see instead? The debugger breaks when the promise is rejected. The trace (given by `console.trace`) when it is rejected looks like: ``` Trace at eval (eval-7c2224bb.repl:1:9) at Object.reject (<anonymous>) at writableStreamRejectCloseAndClosedPromiseIfNeeded (node:internal/webstreams/writablestream:771:28) at writableStreamFinishErroring (node:internal/webstreams/writablestream:903:5) at writableStreamStartErroring (node:internal/webstreams/writablestream:755:5) at writableStreamDefaultControllerError (node:internal/webstreams/writablestream:1202:3) at WritableStreamDefaultController.error (node:internal/webstreams/writablestream:502:5) at Socket.<anonymous> (node:internal/webstreams/adapters:195:18) at Socket.<anonymous> (node:internal/util:538:20) at Socket.onclose (node:internal/streams/end-of-stream:152:25) ``` The stack on the error object is: ``` 'AbortError: The operation was aborted at handleKnownInternalErrors (node:internal/webstreams/adapters:111:14) at Socket.<anonymous> (node:internal/webstreams/adapters:179:13) …