[Pleasurecruise]

Fixes #539

prepareBundledBuildOutput bundles framework Worker output again with a plain Vite lib build. It now matches @cloudflare/vite-plugin in two ways:

• Additional modules. A plugin applies the Cloudflare Vite plugin's module rules: .wasm and .wasm?module, .bin, .txt, .html and .sql, including # subpath imports that resolve to them. Matching imports stay external, and each file is emitted beside the bundle with a path relative to the chunk that imports it. copyBundle already uploads these files as wasm, data and text modules. The Cloudflare plugin does not export its rules, so the plugin repeats them.
• Resolve conditions. The build uses WORKER_CONDITIONS, which Void's other Worker bundles already use. The constant moves from wrapper.ts to its own module so that cf-build-output.ts still loads Vite lazily.

Both changes apply to every bundle that prepareBundledBuildOutput builds, including the static Worker.

Tests

packages/void/test/unit/cf-build-output.test.ts:

• A framework Worker with wasm-bindgen-style and plain Wasm, text and data imports, a # subpath import and a dynamic import produces wasm, text and data modules and passes the cf dry run.
• A dependency with workerd and browser exports resolves to its workerd build.

Each test fails when its change is removed. vp run test, vp run --filter ./packages/void typecheck, vp lint and vp fmt --check pass.

I also prepared the output of a SvelteKit app that uses @resvg/resvg-wasm and micromark: index_bg.wasm is uploaded as a wasm module, and the bundle contains the Worker build of decode-named-character-reference.