[v22.3.x] Backport 5994 66

[alenkacz]

When kafka api has tls enabled, we don't properly configure pandaproxy and schema registry clients to connect to kafka via these private listeners which meant that it did not work. This PR adds the missing parts of configmap and mounts the missing certificates to make it possible for pp/sr to connect.

For mTLS we need both node cert (if self signed - so that client can verify node cert) and also client certs mounted.

Example redpanda node boostrap config when internal kafka listener has enabled Require Client Auth option:

pandaproxy:
    pandaproxy_api:
        - address: 0.0.0.0
          port: 8082
          name: proxy
pandaproxy_client:
    brokers:
        - address: cluster-0.cluster.local
          port: 123
    broker_tls:
        key_file: /etc/tls/certs/ca/tls.key
        cert_file: /etc/tls/certs/ca/tls.crt
        truststore_file: /etc/tls/certs/ca.crt
        enabled: true
schema_registry:
    schema_registry_api:
        - address: 0.0.0.0
          port: 8081
          name: schema-registry
schema_registry_client:
    brokers:
        - address: cluster-0.cluster.local
          port: 123
    broker_tls:
        key_file: /etc/tls/certs/ca/tls.key
        cert_file: /etc/tls/certs/ca/tls.crt
        truststore_file: /etc/tls/certs/ca.crt
        enabled: true

Fixes #5994

Backports Required

• none - not a bug fix
• none - issue does not exist in previous branches
• none - papercut/not impactful enough to backport
• v22.3.x
• v22.2.x
• v22.1.x

UX Changes

Release Notes

Bug Fixes

• Fixes pandaproxy and schemaregistry integration with redpanda when TLS is enabled on internal listener

[piyushredpanda]

@alenkacz : This is all good to merge? If so, please do so. We might be cutting a minor first week of Jan and would be great to have this.

[BenPope]

This is a backport of #7820