fix: install ring as the default rustls provider (#61)

[vb1704]

Fixes #61.

patches/matrix-rust-sdk-ring-provider.patch switches matrix-sdk's reqwest to rustls-no-provider, which stops reqwest from installing a crypto provider. Nothing else installs one, so since 0.10.1 every HTTP request fails with "No provider set" and restoreSession can't complete.

This adds one hunk to that patch: HttpSettings::make_client installs ring as the process-wide default before building the reqwest client:

let _ = rustls::crypto::ring::default_provider().install_default();

• It runs before any request, and before the Android-only rustls::ClientConfig::builder() in android_setup_webkpi_verifier, which also needs a default provider.
• install_default returns an error only when a provider is already installed (for example if an app installs its own), so ignoring it is safe and keeps the call idempotent.
• rustls with the ring feature is already a non-wasm dependency added by the same patch, so no Cargo changes are needed.

The rest of the patch is unchanged; the regenerated file applies cleanly with git apply --check to matrix-rust-sdk at 1c44fb66 (matrix-sdk-0.18.0).

Testing: I haven't built the bindings locally (no Rust toolchain on this machine), so this needs a CI or local build to confirm. For context, we hit both issues on Android (React Native 0.84, Android 16): 0.10.0 crashes in aws-lc's jitter entropy on the first TLS handshake, and 0.10.1 fails with "No provider set".

[vb1704]

Closing as a duplicate of #62, which makes the same change and was opened first; sorry for missing it. We're building #62's branch for Android now and will report the result there (React Native 0.84, Android 16).