qbzd: install the rustls process-level CryptoProvider

The rustls crypto provider was not installed for `qbzd`, which caused the
process to panic:

> thread 'tokio-rt-worker' (15737) panicked at [...]/rustls-0.23.37/src/crypto/mod.rs:249:14:
>
> Could not automatically determine the process-level CryptoProvider from
> Rustls crate features.
> Call CryptoProvider::install_default() before this point to select a
> provider manually, or make sure exactly one of the 'aws-lc-rs' and 'ring'
> features is enabled.
> See the documentation of the CryptoProvider type for more information.

The function `ensure_crypto_provider()` was defined in the `qbz-cast` crate
which is obviously not a dependency of `qbzd`.

This commit moves `ensure_crypto_provider()` to `qbz-app`, calls it from `qbzd`
and updates `qbz` accordingly.

crates/qbz-cast/Cargo.toml

@@ -8,12 +8,6 @@ description = "Casting support for QBZ - Chromecast, DLNA"
 # Chromecast
 rust_cast = "0.21"
 
-# TLS provider selection. rust_cast uses rustls; in the multi-crate binary both
-# the aws-lc-rs and ring providers end up enabled (reqwest pulls ring), so
-# rustls can't auto-pick one and panics on connect. We install aws-lc-rs
-# explicitly before connecting (see `ensure_crypto_provider`).
-rustls = { version = "0.23", features = ["aws_lc_rs"] }
-
 # mDNS discovery
 mdns-sd = "0.11"