feat(experiment): deno:request event in node:http

[CertainLach]

Fresh uses vite in dev mode, and vite uses node:http server for requests

However Fresh itself uses Request/Response objects everywhere, requiring conversions between native and node requests. To avoid that, deno:request event allows access to the original deno request for users of node:http

Fresh counterpart: denoland/fresh#3446

Context:

• Fresh V2 Beta WebSocket upgrade request never reaches server behind vite development environment fresh#3350 (comment)
• Fresh V2 Beta WebSocket upgrade request never reaches server behind vite development environment fresh#3350 (comment)

[CertainLach]

Draft until further course of action is suggested by fresh maintainers

[CertainLach]

At the same time, I would like to get feedback from the Deno side.
As far as I can see, there was no precedents to providing access to deno types from node api, yet there is at least this use-case.

[CertainLach]

I wanted to use extends Event there so that users would use typical e.preventDefault() pattern, but it seems strange to mix node's EventEmitted with browser events.

It would also require both setting pendingResponse and cancelling the event, instead of just setting the response field