cloudflare preset breaks unenv/fetch and node:http polyfills

[pi0]

Environment

unenv v2 nightly with nodeless + cloudflare presets

Reproduction

https://github.com/unjs/unenv/blob/main/test/workerd/tests.mjs#L134

example usage

Describe the bug

A change in #363 causes node:http polyfill to use runtime native node:stream which is incompatible with unenv/fetch polyfills (which essentially breaks H3 v1 and Nitro v2 as soon as they use it anyhow, via upgrade or wrangler transpiling for node_compat_v2)

Additional context

This bug introduced as a hotfix for opennextjs/opennextjs-cloudflare#147 (usage in opennextjs)

This is solvable via #365 to support node:stream for node:http polyfill natively.

Logs

No response

[Tofandel]

This is a similar issue to #328

[pi0]

@Tofandel i think you might want to link it to #365. this issue is new and not specific to supporting Express via direct fetch.

[Tofandel]

It's new but I think it breaks in the same way now, than it breaks with Express, because a mix of polyfill and native implementation causes prototype issues which don't have access to the underlying node internal symbols

So the fix for this issue could apply to both and be ported to the node preset