Add volsync environment for testing

This environment can be used to debug the volsync addon.

We add the minikube volumesnapshots and csi-hostpath-driver addons[1],
so we can careate sanpshots with minikube builtin hostpath storage.
With both addons we can create a busybox app with `csi-hostpath-sc`
storage class, and replicate it using `volsync`.

[1] https://minikube.sigs.k8s.io/docs/tutorials/volume_snapshots_and_csi/

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

test/README.md

@@ -567,6 +567,7 @@ simpler and faster to work with a minimal environment.
 - `ocm.yaml` - for testing `ocm` deployment
 - `rook.yaml` - for testing `rook` deployment
 - `submariner.yaml` - for testing `submariner` deployment
+- `volsync.yaml` - for testing `volsync` deployment
 
 ## Testing drenv
 

test/envs/volsync.yaml

@@ -0,0 +1,26 @@
+# SPDX-FileCopyrightText: The RamenDR authors
+# SPDX-License-Identifier: Apache-2.0
+
+# Enviroment for testing volsync deployment.
+---
+name: volsync
+
+templates:
+  - name: cluster
+    driver: kvm2
+    container_runtime: containerd
+    network: default
+    memory: 4g
+    disk_size: 50g
+    addons:
+      - volumesnapshots
+      - csi-hostpath-driver
+    workers:
+      - addons:
+          - name: volsync
+
+profiles:
+  - name: dr1
+    template: cluster
+  - name: dr2
+    template: cluster