TLS Hostname verification doesn't get disabled if using https lookup in PulsarClient

[ivankelly]

Describe the bug
If you connect to a broker using a https lookup url, and the cert doesn't match the hostname, and hostname verification is disabled, it will complain about the hostname.

To Reproduce
Steps to reproduce the behavior:

1. Configure a cluster with TLS authentication. The broker hostname shouldn't match the cert CN.

PulsarClient.builder()
            .serviceUrl("https://BROKER_HOSTNAME:8443")
            .enableTlsHostnameVerification(false)
            .authentication("org.apache.pulsar.client.impl.auth.AuthenticationTls",
                                     "tlsCertFile:PATH_TO_CERT,tlsKeyFile:PATH_TO_KEY")
            .tlsTrustCertsFilePath(PATH_TO_CA).build();

3. The client will fail to connect and give an error about the hostname.

Expected behavior
It shouldn't try to verify the hostname.

[devinbost]

@ivankelly Is this also an issue with

.serviceUrl("pulsar+tls://BROKER_HOSTNAME:6651")

?

[tisonkun]

cc @nodece is it still relevant now?

[nodece]

Closed by #15824.