Wasm Feature Branch

[insipx]

Tracking #942

closes #940 #941 #1038 #1034 #1104

• refactors EncryptedMessageStore into traits & exposes a type alias depending on compile target
• refactors StreamHandles into traits & exposes type alias depending on compile target
• adds CI-adjacent cargo clippy to ./dev/lint-rust script
• All crates apart of same workspace, dep management easier
• Introduce trait, ScopedGroupClient held on MlsGroup
• Add Client as a field to MlsGroup
  • MlsGroup accesses client methods through ScopedGroupClient. This keeps
    the distinction between MlsGroup and Client clear (while also erasing type parameters), while opening it up to
    future refactors where we pull MlsGroup further away from client. (The subset of functions MlsGroup relies on from Client is actually rather small src/groups/scoped_client.rs)

Much of this PR is changing attributes to account for webassembly (tokio-test vs wasm_bindgen::test, etc.)

Some more interesting bits to pay attention to:

• encrypted_store/mod.rs, encrypted_store/native.rs, encrypted_store/wasm.rs, groups/scoped_client.rs and stream_handles.rs. Some smaller changes to subscriptions.rs
  • There's probably a better way to organize encrypted_store/mod.rs, however the current way keeps the details well away from the Client or any code using the store. From the outside, it looks like nothing really changed.

the patch dependency for openssl-sys was never being applied, (latest kotlin build for affected target):

warning: Patch `openssl-sys v0.9.92 (https://github.com/xmtp/rust-openssl.git?branch=clone-v0.9.92#00dacb93)` was not used in the crate graph.
Check that the patched package version and available features are compatible
with the dependency requirements. If the patch has a different version from
what is locked in the Cargo.lock file, run `cargo update` to use the new
version. This may also occur with an optional dependency that is not enabled.

We have an openssl dependency for sqlite. after bringing all crates into the workspace, I was able to pin it:

It might be better to remove this pin entirely. We haven't been using it at all up until now, and pinning to an older openssl version feels wrong

cargo tree -i openssl-sys
openssl-sys v0.9.92
├── libsqlite3-sys v0.29.0
│   ├── diesel v2.2.0 (https://github.com/xmtp/diesel?branch=insipx/sqlite-replace-ignore-pub#78ece4f8)
│   │   ├── diesel_migrations v2.2.0 (https://github.com/xmtp/diesel?branch=insipx/sqlite-replace-ignore-pub#78ece4f8)
│   │   │   └── xmtp_mls v0.1.0 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/xmtp_mls)
│   │   │       ├── bindings_node v0.0.1 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/bindings_node)
│   │   │       ├── bindings_wasm v0.0.1 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/bindings_wasm)
│   │   │       ├── mls_validation_service v0.0.1 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/mls_validation_service)
│   │   │       ├── xmtp_cli v0.1.0 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/examples/cli)
│   │   │       └── xmtpv3 v0.0.1 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/bindings_ffi)
│   │   │       [dev-dependencies]
│   │   │       └── xmtpv3 v0.0.1 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/bindings_ffi)
│   │   └── xmtp_mls v0.1.0 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/xmtp_mls) (*)
│   └── xmtp_mls v0.1.0 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/xmtp_mls) (*)
├── openssl v0.10.57
│   └── xmtp_mls v0.1.0 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/xmtp_mls) (*)
└── xmtp_mls v0.1.0 (/Users/insipx/Projects/xmtp/workspace-libxmtp/wasm-backend/xmtp_mls) (*)

vs main:

❯ cargo tree -i openssl-sys
warning: Patch `openssl-sys v0.9.92 (https://github.com/xmtp/rust-openssl.git?branch=clone-v0.9.92#00dacb93)` was not used in the crate graph.
Check that the patched package version and available features are compatible
with the dependency requirements. If the patch has a different version from
what is locked in the Cargo.lock file, run `cargo update` to use the new
version. This may also occur with an optional dependency that is not enabled.
openssl-sys v0.9.102
└── libsqlite3-sys v0.29.0
    ├── diesel v2.2.2
    │   ├── diesel_migrations v2.2.0
    │   │   └── xmtp_mls v0.0.1 (/Users/insipx/Projects/xmtp/workspace-libxmtp/main/xmtp_mls)
    │   │       └── xmtpv3 v0.0.1 (/Users/insipx/Projects/xmtp/workspace-libxmtp/main/bindings_ffi)
    │   │       [dev-dependencies]
    │   │       └── xmtpv3 v0.0.1 (/Users/insipx/Projects/xmtp/workspace-libxmtp/main/bindings_ffi)
    │   └── xmtp_mls v0.0.1 (/Users/insipx/Projects/xmtp/workspace-libxmtp/main/xmtp_mls) (*)
    └── xmtp_mls v0.0.1 (/Users/insipx/Projects/xmtp/workspace-libxmtp/main/xmtp_mls) (*)

[nplasterer]

Sorry about the conflicts I think these are from my dms branch. 😬