AsyncLocalStorage instance shared between several http requests

### Version v17.5.0 ### Platform Linux DESKTOP 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ### Subsystem async_hooks ### What steps will reproduce the bug? Opening `localhost:3000/` in Chrome (keep-alive) shows that we have access to the same instance of AsyncLocalStorage when we serve both `/` and `/favicon.ico`. I would understand if both of them were coming from the same async resource representing connection and there was no distinction, but log (see below) produced by async hooks shows that there was two separate `HTTPINCOMINGMESSAGE` but when it comes to `request` listener suddenly we have same `asyncId`. May be it is not a bug, but observed behavior is very confusing. I've read that ```js import * as http from "node:http"; import * as events from "node:events"; import * as async_hooks from "node:async_hooks"; await events.once(http.createServer(httpHandler).listen(3000), "listening"); console.log("server started"); const currentRequest = new async_hooks.AsyncLocalStorage(); // Create hook to ensure t async_hooks .createHook({ init(asyncId, type) { if (type === "TickObject" || type === "TickTimeout") return; console.log(asyncId, type); }, }) .enable(); function getCurrentRequestExn() { const current = currentRequest.getStore(); if (!current) throw new Error("no current request"); return current; } function setCurrentRequest(req) { console.log( "setCurrentRequest %s %d", req.url, async_hooks.executionAsyncId() ); const existing = currentRequest.getStore(); if (existing !== void 0) throw new Error("current request already set"); currentRequest.enterWith(req); } function httpHandler(req, res) { setCurrentRequest(req); if (req.url === "/") res.end(route1()); else if (req.url === "/favicon.ico") res.end(route2()); } function route1() { const req = getCurrentRequestExn(); return "route1 " + req.url; } function route2() { const req = getCurrent…