http: publish to http.server.* diagnostics_channel channels - #29588

The `emitResponseFinishChannel` listener is registered (line 685) *after* `endSocketOnFinishIfNeeded` (line 666), so on the `kMustCloseConnection` path (HTTP/1.0, `Connection: close`, `shouldKeepAlive=false`, close-delimited body, etc.) `socket.end()` runs before the channel publishes — a subscriber sees `payload.socket.writableEnded === true` where Node shows `false` (Node's `resOnFinish` publishes as its first action, before `socket.destroySoon()`). Practical impact is near-zero, but moving th

Moving the `response.created` publish into the `ServerResponse` constructor is correct per Node, but it now also fires from `connectionListenerHTTP1` in `src/js/node/http2.ts:5526` (the `Http2SecureServer({allowHTTP1: true})` HTTP/1 fallback). That path doesn't go through `onNodeHTTPRequest`, so it never publishes `http.server.request.start` or attaches the `response.finish` listener — an APM subscriber pairing created↔finish will now see orphaned `response.created` events on this path (Node rou