Research debug tools for WASM

Debugging and dealing with rust-to-WASM code can be a bit hard. For example, there isn't full support for debugging symbols like DWARF for Linux/Mac, and error messages
can be hard to understand. But, I think we can do better, there are a couple of interesting options to look into:

1. [The gloo crate](https://github.com/ranile/gloo?tab=readme-ov-file#goals): useful set of tools for WASM.
2. [wasm-logger](https://crates.io/crates/wasm-logger), if we can't have debug symbols or access to a proper debugger, we can fallback to use log statements
and even have a flag to enable debug logs which can be really helpful when dealing with errors.
3. [console_log](https://docs.rs/console_log/latest/console_log/) ditto, but another crate to research.
4. There are a [couple of blog posts](https://developer.chrome.com/docs/devtools/wasm) from the Chrome docs to debug WebAssembly with debug symbols.

The issue is about researching debug tools for Rust-to-WASM code. Start by exploring the linked resources: the gloo crate, wasm-logger, console_log, and Chrome DevTools documentation for WebAssembly. The goal is to evaluate these options for the Miden web SDK, likely to improve debugging workflows. 'Done' means providing a summary or recommendation based on the research.

Rédigé par le modèle d'indexation à partir du texte de l'issue.