Develop a wasm-able SDK with JS bindings

[neotheprogramist]

Prerequisite

This development initiative is contingent upon the completion of the extension of the OpenZeppelin Cairo Contract to support multiple signers, as detailed in Issue #14.

Objective

1. SDK Development: We aim to create an SDK that's wasm-able, allowing for the generation of JavaScript bindings. This will facilitate developers in interacting seamlessly with the updated account contract.

2. Reference: The current equivalent of our goal for the SDK can be found at cartridge-gg/cartridge webauthn.ts.

3. Integration with starknet-rs: The SDK should encapsulate the functions provided by starknet-rs.

4. Future Provisions: An essential future upgrade would be the capability of the SDK to generate session tokens.

5. Wasm Compatibility: Ensure compatibility with Rust's no_std to confirm wasm-ability.

Acceptance Criteria

• SDK can be translated to wasm and is in line with Rust's no_std.
• Creation of JavaScript bindings for the SDK is smooth and hassle-free.
• Incorporation of functionalities from starknet-rs.
• Potential addition of session token generation in upcoming versions.
• SDK functionalities are parallel to cartridge-gg/cartridge webauthn.ts.