fix(fetch): do not crash on a late request-socket error

[Lazizbek Ergashev (lazerg)]

Summary

• When a server sends its response and then resets the connection without reading the request body (as workerd does when it refuses an oversized or rate-limited upload before consuming it), Node completes the response and detaches the request from its socket. The still-pending write of the unread body then errors on that socket, and with nothing listening for it the process exits with an unhandled write ECONNRESET that a try/catch around the call never sees.
• Keep an error listener on the request socket so this late error no longer reaches the process. The response is already in hand by then, so the request resolves with it (or rejects through the normal request-failure path) instead of taking down the whole process.

Fixes#42074

[Yury Semikhatsky (yury-s)]

See #42116