Add velero configuration to ramenctl config

Velero uses the same s3 bucket using the same s3 profile, but it needs a
different secret stored at `veleroNamespaceSecretKeyRef`.  The secret is
created by `velero install`.

Seems to be complete, but not tested with ramen yet.

Signed-off-by: Nir Soffer <nsoffer@redhat.com>

ramenctl/ramenctl/resources/configmap.yaml

@@ -30,6 +30,8 @@ data:
       catalogSourceName: ramen-catalog
       catalogSourceNamespaceName: ramen-system
       clusterServiceVersionName: ramen-dr-cluster-operator.v0.0.1
+    kubeObjectProtection:
+      veleroNamespaceName: velero
     s3StoreProfiles:
     - s3ProfileName: minio-on-dr1
       s3Bucket: bucket
@@ -38,10 +40,16 @@ data:
       s3SecretRef:
         name: ramen-s3
         namespace: ramen-system
+      veleroNamespaceSecretKeyRef:
+        key: cloud
+        name: cloud-credentials
     - s3ProfileName: minio-on-dr2
       s3Bucket: bucket
       s3CompatibleEndpoint: $minio_url_dr2
       s3Region: us-east-1
       s3SecretRef:
         name: ramen-s3
         namespace: ramen-system
+      veleroNamespaceSecretKeyRef:
+        key: cloud
+        name: cloud-credentials