Remote debug fails in chrome browser Godot 4.3

### Tested versions

Reproducible in 4.3

### System information

Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4070 Ti (NVIDIA; 32.0.15.6614) - AMD Ryzen 9 7950X 16-Core Processor (32 Threads)

### Issue description

Remote debug works for Firefox and Edge browsers, but fails for Chrome browser.

The following error is logged in the web debugger:

Uncaught (in promise) TypeError: WebAssembly.instantiate(): Import #0 "a": module is not an object or function
at tmp_js_export.js:153:17

This has happened for any project I have exported in Godot 4.3.
Couldn't find an issue for it, so wasn't sure if this was known or if others don't have this issue.
Projects work fine in chrome once they are hosted on an external site such as itch.io. It just fails to load in the debugger.

Thanks!

### Steps to reproduce

- Open any Godot project.
- Export to Web.
- Run remote debugger

### Minimal reproduction project (MRP)

[new-game-project.zip](https://github.com/user-attachments/files/18044245/new-game-project.zip)

Use the attached new-game-project.zip to reproduce the Web export remote-debug failure in Chrome, then compare the same project in Firefox and Edge. Start with the web debugger error at tmp_js_export.js:153 and the WebAssembly.instantiate import failure. Done means remote debugging loads the exported project in Chrome as it already does in the other browsers.

Written by the indexing model from the issue text.