Warn when ignoring connection string parameters or scheme

@Michael Reiche My guess is `tlsEnabled` exists because shared environments can't be configured using a connection string, so some other way was required.

I see an argument for `tlsEnabled` being coerced to true if a trust source is specified (why specify a trust source if you're not using TLS?) or at least logging a warning.

In the short term, the separate `tlsEnabled` flag is useful because the Capella CA certificate is bundled with the SDK, and it lets people use TLS without explicitly specifying a trust source.

There are certainly things we could do to improve the ergonomics in this area... let's track them separately. https://couchbasecloud.atlassian.net/browse/JCBC-1928#icft=JCBC-1928 is a great start.

Why does the tlsEnabled property exist? Isn't the existence of a certificate path sufficient for determining whether or not tls should be used? The separate tlsEnabled property implies there is a use-case for specifying a certificate path, but not using tls.