Conditional deployment of minio operator console pro-grammatically

[shtripat]

Fixes: #1598

Allow conditional deployment of operator console through helm.

Steps to verify the change

1. Set .Values.operator.console value as false in helm/operator/values.yaml

console:
  enabled: false
  image:
    repository: quay.io/minio/operator
    tag: v5.0.9
    pullPolicy: IfNotPresent
  env: [ ]

2. Install minio operator

$ helm install --namespace minio-operator --create-namespace minio-operator ./helm/operator

3. Deploy a MinIO tenant

$ kubectl create ns tenant-ns
$ kubectl minio tenant create tenant1 --servers 4 --volumes 4 --capacity 2Gi --namespace tenant-ns

4. Create an alias to the MinIO tenant, create a bucket and load an object

$ kubectl get secrets/tenant1-user-1 -n tenant-ns -oyaml | yq '.data.CONSOLE_ACCESS_KEY' | base64 -d
JF9HAHTV2596PC6PGWPU
$ kubectl get secrets/tenant1-user-1 -n tenant-ns -oyaml | yq '.data.CONSOLE_SECRET_KEY' | base64 -d
j7ohF4tdcBvt3SdApxbhNbvldYMItJbVeDfrr0Gn

$ kubectl port-forward svc/minio -n tenant-ns 9443:443

$ mc alias set myminio https://localhost:9443 JF9HAHTV2596PC6PGWPU j7ohF4tdcBvt3SdApxbhNbvldYMItJbVeDfrr0Gn --insecure
$ mc mb myminio/test-bucket --insecure
$ mc cp /etc/issue myminio/test-bucket --insecure

5. Port forward to console service ad open MinIO object browser console and verify the bucket and object

$ kubectl port-forward svc/tenant1-console -n tenant-ns 9000:9443