Fixed tls connection issue

[shustsud]

Motivation

I tried a tls connection but it failed.

Log:

$ go run producerForTls.go
pulsar.NewClient start.pulsar.NewClient end.INFO[0000] Connecting to broker                          remote_addr="pulsar+ssl://<hostname>:6651"
INFO[0000] TCP connection established                    local_addr="<ip>:<port>" remote_addr="pulsar+ssl://<hostname>:6651"
INFO[0000] Connection is ready                           local_addr="<ip>:<port>" remote_addr="pulsar+ssl://<hostname>:6651"
INFO[0000] Connecting to broker                          remote_addr="pulsar://<hostname>:6650"
WARN[0000] Failed to connect to broker.                  error=EOF remote_addr="pulsar://<hostname>:6650"
INFO[0000] Connection closed                             remote_addr="pulsar://<hostname>:6650"
INFO[0002] Connecting to broker                          remote_addr="pulsar://<hostname>:6650"
WARN[0002] Failed to connect to broker.                  error=EOF remote_addr="pulsar://<hostname>:6650"
INFO[0002] Connection closed                             remote_addr="pulsar://<hostname>:6650"
INFO[0006] Connecting to broker                          remote_addr="pulsar://<hostname>:6650"
WARN[0006] Failed to connect to broker.                  error=EOF remote_addr="pulsar://<hostname>:6650"
INFO[0006] Connection closed                             remote_addr="pulsar://<hostname>:6650"

After Lookup, the url seems to use BrokerServiceUrl.
If use tls connection, I think url will use BrokerServiceUrlTls.

Modifications

• Fixed Lookup service.

Verifying this change

• Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API: (no)
• The schema: (no)
• The default values of configurations: (no)
• The wire protocol: (no)

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not applicable)