How to deal with cargo features of HTTP client crates?

[frigus02]

opentelemetry-application-insights requires users to bring an HTTP client. opentelemetry-http brings implementations for reqwest, surf and isahc currently. But users are free to implement the corresponding trait for other HTTP clients, too. Each HTTP client crate may have cargo features.

opentelemetry-application-insights started adding "proxy" features for some reqwest features:

opentelemetry-application-insights/Cargo.toml

Lines 29 to 30 in 1e5727a

	reqwest-client-vendored-tls = ["opentelemetry-http/reqwest", "reqwest/native-tls-vendored"]
	reqwest-client-rustls = ["opentelemetry-http/reqwest", "reqwest/rustls-tls"]

But doing that for all clients and all their features doesn't seem maintainable.

I would like to:

• Figure out how users are supposed to enable features for the HTTP client crate of their choosing.
• Make this clear through documentation.