Support creating mTLS certificates between KIC and Kong admin APIs in installation

[randmonkey]

From FTI-5816.
Customer wants to create the mTLS certificates between KIC and Kong admin APIs and use it in one helm install command.
For example, customers can create such a values.yaml and install KIC by the kong/ingress charts, then the CA certificates and client certificates for mTLS are created and used between KIC and Kong admin APIs.

controller: 
 ingressController:
    adminApi:
      tls:
        client:
          enabled: true
          certProvided: false
gateway:
  admin:
    tls:
      client:
        secretName: <release name>-controller-admin-api-ca-keypair

Currently customers has to create the certificates with the values removing the gateway.admin.tls.client.secretName:

controller: 
 ingressController:
    adminApi:
      tls:
        client:
          enabled: true
          certProvided: false

Then add back gateway.admin.tls.client.secretName in the values and upgrade the release. This is not convenient so customers want to have a way to create and use mTLS certificates by a single helm install command.

[sandromodarelli]

punting to KO 2.0.x as agreed with @justindavies

[programmer04]

Since the customer resolved this issue for his setup. Now KO is the only product, and it handles mTLS by design. So when you have such a requirement, just use KO. KIC and its Helm Chart are in maintenance mode now.

Thus, I think we can close this issue and FTI-5816 as not planned.
WDYT @randmonkey?