rustls feature additivity issue

rustls allows the choice of ring or aws-lc-rs as the cryptographic library implementation. This is enabled/selected via Cargo feature flags. We have plugins directly or indirectly depending on rustls like quinn, aws and spotify.

In the presence of two plugins, selecting different implementations as the default, one may encounter a runtime panic. Related issue is described here. See !1801 (merged) for an occurrence of this issue.

Library authors explicitly selecting the provider with builder_with_provider seems like a possible solution?.