[Bug] No CryptoProvider configured for rustls for websocket

[mattsse]

Component

provider, pubsub

Describe the feature you would like

tungstenite depends on a newer version of rustls than reqwest and now disables rustls default features: snapview/tungstenite-rs#427 and expects the user to pick a backend.

hence wss connections currently fail with:

no process-level CryptoProvider available -- call CryptoProvider::install_default() before this point

we can solve this by

a) downgrading tokio-tungstenite
b) choosing a backend (ring) by depending on rustls in transport-ws
c) expect the user to do this (I don't want any issues for this)

wo could do a) until reqwest also updates its rustls dep this way we also don't pull in rustls twice

Additional context

No response