Tracking issue: Stabilizing network inspection in Node.js

Related issue: https://github.com/nodejs/diagnostics/issues/75 Initial implementation: https://github.com/nodejs/node/pull/53593 This issue is for tracking the remaining work to make network inspection in Node.js stable and to provide a comprehensive debugging experience. # Network inspection features - ✅ - Implemented - 🚫 - No plan to implement at the moment - 🔍 - Need further investigation or discussion ## Basic information | Feature | `http` | `https` | `http2` | `fetch` | `WebSocket` | | --- | --- | --- | --- | --- | --- | | type | ✅ #54156 | ✅ #54156 | ✅ #59611 | ✅ #56488 | ✅ #59404 | | timestamp | ✅ #53593 | ✅ #53593 | ✅ #59611 | ✅ #56488 | ✅ #59404 | | error | ✅ #54246 | ✅ #54246 | ✅ #59611 | ✅ #56488 | | Related protocols: - `Network.requestWillBeSent` - `Network.responseReceived` - `Network.loadingFinished` - `Network.loadingFailed` - `Network.webSocketCreated` - `Network.webSocketClosed` - `Network.webSocketFrameError` ## Request details The details of the request, such as the request body, cookies, and query parameters. The [`Network.Request`](https://chromedevtools.github.io/devtools-protocol/tot/Network/#type-Request) object is used to represent the request. Some features such as `referrerPolicy` are only available in browser contexts. | Feature | `http` | `https` | `http2` | `fetch` | `WebSocket` | | --- | --- | --- | --- | --- | --- | | url | ✅ #53593 | ✅ #53593 | ✅ #59611 | ✅ #56488 | | | method | ✅ #53593 | ✅ #53593 | ✅ #59611 | ✅ #56488 | | | headers | ✅ #54156 | ✅ #54156 | ✅ #59611 | ✅ #56488 | | | postData | 🔍 | 🔍 | ✅ #60483 | | | Related protocols: - `Network.requestWillBeSent` - `Network.websocketFrameSent` - `Network.webSocketWillSendHandshakeRequest` ## 🔍 Response details The details of the response, such as the response body, and headers. The [`Network.Response`](https://chromedevtools.github.io/devtools-protocol/tot/Network/#type-Response) object is used to represent the response. Some features such as early hits are only availa…