fix: Explicitly set rustls provider before using rustls

[popzxc]

Recently rustls changed default crypto provider from ring to aws-lc-rs, and it caused some crates to depend on both features (e.g. if one dependency uses a default provider, and other one enables ring).
In such cases, rustls would panic, because it can't choose a default provider (see this issue).

This PR makes sure that the provider is set before using rustls functionality, thus preventing panics in runtime.

This isn't the most elegant solution to the problem, but it does fix it (confirmed in my project), so I hope it's fine to merge it as a quickfix.

[niklasad1]

Hey,

Did you try specifying ring = { version = *, default-features = false, features = ["ring", "logging", "std", "tls12"] } in jsonrpsee to fix it?

Or is this the case that some other crate brings in aws-ls-rs and rustls priorities aws-lc-rc when both ring and aws-ls-rc are defined?

Anyway, I'm fine with this hack.

[popzxc]

Or is this the case that some other crate brings in aws-ls-rs and rustls priorities aws-lc-rc when both ring and aws-ls-rc are defined?

Yes, I had both jsonrpsee (which brings ring) and other crate (which brings aws-ls-rs) in deps

[niklasad1]

Thanks @popzxc, we'll release a new version tomorrow.