[bitnami/kafka] Add ClusterIP and loadBalancerNames check for using external access hosts list

[moustafaomar]

Description of the change

This change solves the issue of using kafka with an nginx ingress with different hostnames and a fixed port. The change allows creating ClusterIP services for the external access, while enabling a different way for adding the hostnames using the loadBalancerNames.

Benefits

For restricted kubernetes implementations, where the user can only use a single port, the idea of having the domain field with ports that are automatically incremented doesn't work for the listeners.
This PR helps solve this issue by adding a condition for the service type being ClusterIP and the loadBalancerNames having the domain names, with the fixed port on ports.external.

Possible drawbacks

The only issue with this change is that it still marks the domain field as required for ClusterIP services.

Applicable issues

• fixes [kafka] Unable to set correct advertised listeners for external access behind TCP Ingress #25030

Additional information

To test the change:

• Set externalAccess.controller.service.type and externalAccess.controller.broker.type to ClusterIP
• Fill externalAccess.controller.service.domain and externalAccess.broker.service.domain with any values
• Add externalAccess.controller.service.loadBalancerNames and externalAccess.broker.service.loadBalancerNames with the ingress hostnames.
• Expected output: advertised.listeners on each pod gets EXTERNAL://hostname:port

Checklist

• Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
• Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
• All commits signed off and in agreement of Developer Certificate of Origin (DCO)

[alvneiayu]

Please, bump the version on the Chart.yaml.

[moustafaomar]

Done, changed it to 32.2.17