redpanda connectors subchart to connectors chart migration

values.yaml

# Below is a guide on how to deploy the kafka connectors helm chart now that
# the subchart integration has been removed from both the redpanda helm chart
# and redpanda operator.
#
# 1. Copy the contents of this file into a values.yaml file somewhere.
# 2. Merge contents of the `connectors` key from your redpanda values.yaml into this file, giving precidence to this file.
# 3. Remove the contents of the `connectors` key from your redpanda.values.yaml
# 4. Upgrade your redpanda chart to the target version, the connectors deployment should be removed.
# 5. Deploy connectors as a standalone chart with `helm install redpanda/connectors -f values.yaml --namespace <NAMESPACE> <RELEASE_NAME>`
#
# The values provided are those that would be used to deploy the connecotrs chart with a
# default deployment of the redpanda chart in the `default` Kubernetes namespace.
#
# Each value, unless noted otherwise, is annotated with a JQ expression that
# will extract the appropriate value from a redpanda release's helm values.
#
# A redpanda release's helm values may be retrieved by running `helm get values --namespace
# <NAMESPACE> <RELEASE_NAME> --all -o json`
#
# If using a Redpanda CR, the same jq expression can be run against the
# `clusterSpec` key. In the case of a missing value, fallback to
# checking the output of `helm show values redpanda/redpanda --version <VERSION>`. <VERSION>
# may be obtained by checking the value set in your Redpanda's `chartRef` key
# or by checking the documention of your Redpanda CRD's `chartRef` field.
connectors:
  # A list of BROKER_URL:PORT, comma separated. If uncertain, this can be retried by running:
  # kubectl run -it --restart=Never --rm --image busybox busybox -- ash -c 'nslookup -type=srv _kafka._tcp.<RELEASE_NAME>.<NAMESPACE>.svc.cluster.local | tail -n +4 | head -n -1 | awk \'{print $7 ":" $6}\''
  bootstrapServers: redpanda-0.redpanda.default.svc.cluster.local:9093,redpanda-2.redpanda.default.svc.cluster.local:9093,redpanda-1.redpanda.default.svc.cluster.local:9093
  auth:
    sasl:
      enabled: false # .auth.sasl.enabled
      mechanism: "scram-sha-512" # .auth.sasl.mechanism | ascii_downcase
      # If SASL is enabled, secretRef must refer to a Secret in the same
      # namespace as this chart with a key "password" that contains this SASL
      # user's password.
      secretRef: ""
      # If SASL is enabled, the username of the user to authenticate as.
      userName: ""
  brokerTLS:
    enabled: true # .listeners.kafka.tls.enabled
    # If TLS is enabled, you need to direct the connectors chart at a CA that
    # trusts the certificate in use by redpanda.
    ca:
      # If using the cert-manager integration this follows the format
      # "<RELEASE_NAME>-<.listeners.kafka.tls.cert>-cert".
      secretRef: "redpanda-default-cert"
      # If providing your own certificates, secretNameOverwrite may be used to
      # read from a key other than "ca.crt".
      secretNameOverwrite: "ca.crt"