chore: Enable kube/ring feature

[xeniape]

Needs #987

kube-rs/kube#1717 removed ring as the default crypto provider which was always present even though default features were turned off using default-features = false. Setups which disabled default features without manually specifying the crypto provider using a feature accidentally worked. After kube 0.99.0 was released, these setups broke, as did our one.

The changes needed are outlined in kube-rs/kube#1720.

Runtime error

2025-03-19T14:37:07.285064Z  INFO stackable_operator::utils::logging: Starting Stackable Operator for Apache Superset
2025-03-19T14:37:07.285095Z  INFO stackable_operator::utils::logging: This is version 0.0.0-dev (Git information: c7273b5), built for x86_64-unknown-linux-gnu by rustc 1.84.1 (e71f9a9a9 2025-01-27) at Wed, 19 Mar 2025 14:14:33 +0000
thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.23.25/src/crypto/mod.rs:249:14:
no process-level CryptoProvider available -- call CryptoProvider::install_default() before this point
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace