Bump tungstenite to 0.30 and async-tungstenite to 0.35

[Tryanks]

Supersedes #466 and #470.

Dependabot bumped tungstenite and async-tungstenite separately, so each PR ended up with two tungstenite versions (the one tcode-remote names and the one async-tungstenite re-exports) and the Message types no longer matched. Bumping both in one change resolves to a single tungstenite 0.30.0; async-tungstenite keeps default-features = false with only handshake, which still exists in 0.35. crates/remote needed no source changes because it already builds Message::Text through .into().

Cargo.lock only picks up the two bumps plus their transitive closure (sha1 0.11 / rand 0.10 for tungstenite); an unrelated tempfile → getrandom re-resolution that cargo update -p produced was reverted.

Local evidence (macOS arm64):

• cargo fmt --all --check ✅
• cargo clippy --workspace --all-targets --locked -- -D warnings ✅
• cargo build --workspace --locked ✅
• cargo test --workspace --locked ✅
• cargo machete ✅