Create drenv end-to-end failover/relocate test using VRG `KubeObjectProtection` without OCM

[hatfieldbrian]

kubeObjectProtection requirements

1. Velero controller v1.9 or greater installed and running in each cluster
2. Velero controller namespace name specified in Ramen config map's kubeObjectProtection section else default velero
3. Velero BackupStorageLocation, Backup, and Restore CRDs installed in each cluster
   • Note: Ramen only watches Velero's Backup and Restore resources, not its BackupStorageLocations
4. S3 credentials in a secret in the Velero controller namespace in a key with the following AWS format

   [default]
   aws_access_key_id=<AWS_ACCESS_KEY_ID>
   aws_secret_access_key=<AWS_SECRET_ACCESS_KEY>

   • Note: A VRG's spec.s3Profiles are used for both native PV/PVC protection and Velero-based kubeObjectProtection, but their secret file formats differ
5. Velero S3 credentials secret reference specified in Ramen config map's s3StorePofiles section for each profile specified in VRG spec.s3Profiles

kubeObjectProtection non-requirements

1. Open/Advanced Cluster Management
2. A hub cluster

Test requirements

1. Stateful application, e.g., busybox-sample, initial deployment
2. Specify VRG spec.kubeObjectProtection field
   • A 1m or less captureInterval is recommended; default is 5m

[nirs]

903 adds an environment with velero and without a hub. It can be used to create the test

suggest in this issue.