[Bug] SSL initialization errors when having TLS ports without TLS configs

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Read release policy

- [X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

### Version

4.0.0-preview.1

### Minimal reproduce step

Configure a broker with TLS deactivated but TLS port defined.

### What did you expect to see?

Nothing wrong (as in the previous version).

### What did you see instead?

https://gist.githubusercontent.com/KannarFr/fa521bf61e92d8801a08d7505e9c9b2c/raw/0690469c7c05d93a91da92f3f4d7e3620c600157/gistfile1.txt

### Anything else?

Set empty in TLS ports fixes the issue.

Probably related to https://github.com/apache/pulsar/blob/master/pip/pip-337.md.

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Reproduce the broker startup with TLS deactivated while a TLS port is defined, using the 4.0.0-preview.1 setup and the startup output in the linked gist. Read pip/pip-337.md for the related configuration context; done means startup no longer reports SSL initialization errors and the prior behavior is preserved.

Written by the indexing model from the issue text.