fix(cloudflare): wasm support with dynamic chunks

[pi0]

🔗 Linked issue

#1952

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This is almost a rewrite of #1565 in order to support WASM (via native ESM imports) for Cloudflare modules and page environments.

As of #1905, we have enabled dynamic chunks by default for Cloudflare modules and pages. As a result, the wasm imports need to be resolved relative to the chunk paths like ../wasm/* rather than ./wasm/*. This required significant changes.

The rollup preferred way is using File URLs i tried this method but import.meta.ROLLUP_FILE_URL_* if conflicting with nitro plugin today + not sure if using new URL for imports is supported for wrangler static analyzer for .wasm entries. As alternative way, i used an AST parser to post normalize nitro specific ids (\0nitro:wasm\) to real wasm path.

Another note: Since tests enabled, i had pushed two more hooks to the plugin that somehow allows wasm for IIFE preset cloudflare. It shouldn't work (!) but wrangler dev (both local and remote) allows this!

A new importWasm utility is also added to test fixture subject to extract as reusable auto imported util in next iterations.

This PR also fixes windows compatibility issue detected via tests / disabled in e73b849

Tests for workers are still disabled due to the limitations of current setup so i used local tests.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.