fix: rust 1.95.0 clippy lints and matrix-sdk 0.17 API changes

Toolchain bump surfaced new lints (derivable_impls,
unnecessary_unwrap, unnecessary_sort_by, while_let_loop,
collapsible_match, unnecessary_option_map_or_else, cmp_owned)
across bft-json-crdt and huskies-server. All fixed mechanically.

Cargo.toml: dropped the no-longer-existing `rustls-tls` matrix-sdk
feature, then chased through the 0.17 API breakage:
- Relation::Reply is now a tuple variant wrapping Reply, not a
  struct variant with `in_reply_to`
- UserIdentifier::UserIdOrLocalpart removed — use
  UserIdentifier::Matrix(MatrixUserIdentifier::new(..))
- SendMessageLikeEventResult no longer exposes event_id directly;
  it's now on the inner `response` field

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Cargo.toml

@@ -38,20 +38,7 @@ uuid = { version = "1.23.1", features = ["v4", "serde"] }
 tokio-tungstenite = { version = "0.29.0", features = ["connect", "rustls-tls-native-roots"] }
 walkdir = "2.5.0"
 filetime = "0.2"
-# Pinned to 0.16.x: matrix-sdk 0.17.0 uses Duration::from_mins (stabilised in
-# Rust 1.93) and declares rust-version = "1.93".  Our toolchain is 1.90 and the
-# rustup directory is read-only in this environment, so 0.17 cannot be compiled.
-# Once the image ships Rust ≥1.93, bump this to "0.17" and remove this comment.
-#
-# rand@0.8 residual (unavoidable on 0.16.x): vodozemac v0.9, oauth2 v5, and
-# ruma-common v0.17 all depend on rand 0.8.  These are eliminated in matrix-sdk
-# 0.17 where vodozemac moves to 0.10 and ruma to 0.15; until then the residual
-# is intentional and audited — no hand-rolled crypto is involved.
-#
-# libsqlite3-sys: both matrix-sdk-sqlite 0.16 (via rusqlite 0.37) and sqlx
-# 0.9.0-alpha.1 resolve to libsqlite3-sys 0.35.0; there is no version conflict.
-matrix-sdk = { version = "0.16", default-features = false, features = [
-    "rustls-tls",
+matrix-sdk = { version = "0.17", default-features = false, features = [
     "sqlite",
     "e2e-encryption",
 ] }