Enhance Vite's WebAssembly ESM integration. Direct `.wasm` imports must expose exported `WebAssembly.Global` values to JavaScript as their normal JS values (for example, an i32 global is imported as a number), rather than as `WebAssembly.Global` objects. At the same time, wasm-to-wasm imports must continue receiving the actual live global cell: a module may import another wasm module's global, and mutations from the exporting module must be visible to the consumer.

Enable the WebAssembly JS String Builtins and Imported String Constants proposals for the compilation and instantiation paths used by Vite's wasm support, consistent with the specification and Node.js behavior. Engine-provided builtin and string-constant imports must not be treated as ordinary JavaScript module imports. Preserve existing direct `.wasm` imports and `?init` behavior.