Summary

ClientUtils.clusterClientBaseConfig currently builds the base configuration for internal producers/consumers using only the inter-broker endpoint and the protocol/mechanism. It omits SSL and listener-prefixed security properties, so internal clients fail to connect when the inter-broker listener requires TLS or SASL.

Steps to reproduce

1. Configure a broker with inter.broker.listener.name pointing to a listener that uses SSL or SASL_SSL.
2. Supply the necessary ssl.* properties (e.g., ssl.truststore.location, ssl.keystore.location) under the listener prefix.
3. Start any internal component (e.g., table Channel) that relies on ClientUtils.clusterClientBaseConfig.

Expected result

Internal clients inherit the listener's SSL/SASL settings and connect successfully.

Actual result

The returned lack those SSL/SASL entries, so the handshake fails.

Proposed fix

Merge the global / and listener-prefixed configs into the base client Properties before returning.