BrokerSts: brokerWebServiceURLTLS is not empty on proxy even if you don't enable TLS

[eolivelli]

I have noticed that if you enable brokerSts and you don't enable TLS the helm chart still populates brokerWebServiceURLTLS.
This shouldn't be a problem because you have to set tlsEnabledWithBroker but it is very difficult to understand.

Actually it revealed a bug in Starlight for Kafka, that assumed that if brokerWebServiceURLTLS is non empty, then it is a valid URL to connect to the brokers.

[eolivelli]

I have also noticed a typo here:
https://github.com/datastax/pulsar-helm-chart/blob/master/helm-chart-sources/pulsar/templates/proxy/proxy-ws-configmap.yaml#L34

in this file we use both brokerServiceURL and brokerServiceUrl
the correct spelling should be brokerServiceURL according to the Java source

[eolivelli]

for reference:
datastax/starlight-for-kafka#16