[wasm][debugger] Fetching assemblies in the debug proxy is (possibly) slower now

[radical]

Improve how the proxy acquires the assemblies

With #69072, the debugger tests/chrome started timing out on Windows after 1 hour. Without that PR, they take 35-40mins. (Note: the tests pass on main because the timeout was bumped to 90mins).

• We need to figure out a better way to do this, or fetch the base64 encoded assemblies only when we need them. For example, we could try http, if that's available, and use base64 as a fallback.
• Is there a better way to get these assemblies from the app? IIUC, with the current way (sending in a cdp message), we are limited to that single connection vs multiple parallel downloads in case of fetching via http.
• Is it possible to have multiple cdp connections to the app, to get these?

cc @lewing @thaystg @ilonatommy

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Improve how the proxy acquires the assemblies

With #69072, the debugger tests/chrome started timing out on Windows after 1 hour. Without that PR, they take 35-40mins.

• We need to figure out a better way to do this, or fetch the base64 encoded assemblies only when we need them. For example, we could try http, if that's available, and use base64 as a fallback.
• Is there a better way to get these assemblies from the app? IIUC, with the current way (sending in a cdp message), we are limited to that single connection vs multiple parallel downloads in case of fetching via http.
• Is it possible to have multiple cdp connections to the app, to get these?

cc @lewing @thaystg @ilonatommy

Author:	radical
Assignees:	-
Labels:	arch-wasm, area-Debugger-mono
Milestone:	-