Feature Request: Complete WASM Bindings for Subxt Client

It would be valuable to have comprehensive WASM bindings for Subxt clients, covering transactions, queries, and all types used within the client for operations. The goal would be to generate complete JS/TS bindings via wasm_bindgen for the entire Subxt library, which would make Subxt extremely powerful by enabling direct use of the Subxt interface in JS/TS applications.

Background

This idea emerged from our current effort to centralize all chain-related codebase in Rust. We've been exploring solutions like wasm_bindgen for our existing code, allowing non-Rust web developers to use our Rust-maintained tools. Currently, this requires us to wrap all possible operations using Subxt clients in a context that is JS-compatible and interfaceable (via wasm_bindgen on wrapper types).

Question

Do you think this feature could be implemented in the future? I understand this would be a substantial undertaking, but it would significantly expand Subxt's accessibility to the JavaScript/TypeScript ecosystem, and highly reduce verbosity for future projects that would like to adopt this architecture for their SDK.

No files, tests, or entry points are named. Start by reviewing the existing Subxt client and its wasm_bindgen wrapper approach, then determine how transactions, queries, and client types would be exposed to JavaScript and TypeScript. Done would mean a defined and implemented set of comprehensive bindings for the requested operations.