Problem

server.closeIdleConnections() does not close TCP connections that have been accepted but have not yet sent any HTTP data, contradicting its
documented behavior ("Closes all connections connected to this server which are not
sending a request or waiting for a response") and blocking graceful shutdown when peers (e.g. browsers opening speculative connections) hold
sockets open without writing.

Repro:

import { createServer } from 'node:http';
import { createConnection } from 'node:net';

const server = createServer((req, res) => res.end('ok'));
server.listen(3099, '127.0.0.1');
await new Promise((r) => server.once('listening', r));

const sock = createConnection(3099, '127.0.0.1');
await new Promise((r) => sock.once('connect', r));
await new Promise((r) => server.once('connection', r));

const closed = new Promise((r) => server.close(() => r(performance.now())));
const closeStart = performance.now();
server.closeIdleConnections();

const t = await Promise.race([
  closed,
  new Promise((r) => setTimeout(() => r(null), 2000)),
]);
console.log(t === null ? 'still hung after 2s' : `closed in ${t - closeStart}ms`);
sock.destroy();

Before: still hung after 2s. After: closes immediately.

Reported in #63452.

Cause

New sockets are pushed into kConnections from connectionListenerInternal via parser.initialize(...), but Parser::Initialize
(src/node_http_parser.cc:730) sets last_message_start_ = uv_hrtime() so that headersTimeout / requestTimeout can begin counting (DoS
protection). ConnectionsList::Idle() (src/node_http_parser.cc:1147) only returns parsers with last_message_start_ === 0, which becomes true
only after on_message_complete resets it (line 544). Sockets that were accepted but have not sent any HTTP data are therefore classified as active
and skipped by closeIdleConnections().

Fix

lib/_http_server.js: in addition to the existing idle() iteration, walk all() and destroy any socket whose bytesRead === 0. That uniquely
identifies sockets that have not received any data and so cannot be sending a request or awaiting a response. Keep-alive sockets between requests,
in-flight requests, and in-flight responses all have bytesRead > 0 and are unaffected.

Test

Added test/parallel/test-http-server-close-idle-connections-pre-request.js. It opens a TCP connection without sending any data, calls
server.close() + server.closeIdleConnections(), and uses an unref'd setTimeout(common.mustNotCall(), 1000) as the safety net: if the fix works
the event loop drains and the timer never fires; without the fix the timer fires and the assertion trips.

Verification

$ # apply the patch logic as a runtime override and run the repro
$ ./node /tmp/verify_patch.mjs
after closeIdleConnections, awaiting close...
closed in 0.37ms

A full local build of the patched binary was not completed because this machine has Apple clang 16.0.0, while the current tree requires a newer
toolchain (V8 fails to compile due to missing std::atomic_ref). The behavior change was verified by monkey-patching
Server.prototype.closeIdleConnections with the same logic and running the issue's reproduction.

Fixes: #63452