TLS client default behaviour seems unergonomic

[xd009642]

So we kinda got screwed a bit recently when the url our client connected to became a https URL. Despite having the crate built with tonics rustls features (tls, tls-roots, tls-webpki-roots) we had to change:

let mut client = TextToSpeechClient::connect(url).await.unwrap();

To:

let uri = Uri::try_from(&url.to_string())
    .map_err(|e| Status::internal(format!("Invalid URL: {}", e)))?;

let tls = ClientTlsConfig::new().with_enabled_roots();

let channel = Endpoint::from(uri)
    .tls_config(tls)
    .map_err(|e| Status::internal(format!("TLS config invalid: {}", e)))?
    .connect()
    .await
    .map_err(|e| Status::internal(e.to_string()))?;

let mut client = TextToSpeechClient::new(channel);

And it's a bit like why doesn't connect just use the default TLS if it's available or return an error if the URL uses HTTPS. Because getting h2 protocol error: http2 error isn't great UX if connect can never work with https just return an error earlier, but I'm of the opinion that the default connect should just work with what's maximally available and cheap to setup by default. Reqwest uses TLS by default so I'm not really seeing a compelling reason for tonic to significantly differ