Node >= 16.18.0 breaks npm ci

### Version 16.18.0, 16.19.0, 18.3.0 ### Platform `Linux ip-10-94-32-11 5.15.0-1026-aws #30-Ubuntu SMP Wed Nov 23 14:15:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux` ### Subsystem http ### What steps will reproduce the bug? Execute `npm ci` ### How often does it reproduce? Is there a required condition? I am able to reproduce the issue every single time. ### What is the expected behavior? `npm ci` should execute successfully. ### What do you see instead? ```bash $ npm ci npm ERR! code EPIPE npm ERR! syscall write npm ERR! errno -32 npm ERR! write EPIPE npm ERR! A complete log of this run can be found in: npm ERR! /home/ubuntu/.npm/_logs/2023-01-12T18_17_28_239Z-debug-0.log ``` ### Additional information I originally left a comment on closed issue #44998. In fear that it would never be seen, I've opened a new issue here. I am currently experiencing this issue on any version of node after 16.18.0. I have tried the latest versions from both the 16 and 18 release channels. Using git bisect and building node from source, I have narrowed down the problematic commit to `5f406a3a53: http: reuse socket only when it is drained (3 months ago) <ywave620>`. (associated pull request https://github.com/nodejs/node/pull/43902) When I run npm ci on any branch which includes this commit, I encounter this EPIPE error. If I revert the commit and rebuild node, I can see from the logs that the EPIPE error is still emitted, but it is handled properly. Unfortunately, I'm really not sure what exactly it is about my environment that is causing this EPIPE error, as it doesn't seem like it's affecting very many users at all. I experience the issue running from AWS EC2 or ECS connected to my company's private network using a Transit Gateway. So, there must be something special about my network which triggers this issue. In the meantime, the best I can currently do is attach a set of detailed logs. For each of these sets of logs, I ran `DEBUG='*' NODE_DEBUG='*' npm ci`: * [v16.17.1](https://gi…