feat(validation): adding validation for ZFSPV CR parameters (#66)

Validating few parameters for the ZFSVolume custom resource

- compression can be "on", "off", "lzjb", "gzip", "gzip-[1-9]", "zle" and "lz4"
- encryption can be "on", "off", "aes-128-ccm", "aes-192-ccm", "aes-256-ccm", "aes-128-gcm", "aes-192-gcm", and "aes-256-gcm"
- dedup can be "on" and "off"
- poolname can be string
- ownernodeid can be string
- thinprovision can be "yes" and "no"
- volumetype can be "DATASET" and "ZVOL"

Also added required fields needed to create ZFSVolume CR
- ownerNodeID
- poolname
- volumeType
- capacity


Signed-off-by: Pawan <pawan@mayadata.io>

deploy/yamls/namespace.yaml

@@ -0,0 +1,14 @@
+# Create the OpenEBS namespace
+# This is the default namespace where the ZFS driver will create all
+# its resources. If we want to change it to use a different namespace
+# modify this to create the new namespace and also modify the OPENEBS_NAMESPACE
+# env for the ZFS Driver's controller and agent deployments.
+# please note that this should be changed while initial setup, once ZFS Driver
+# is deployed with a namespace, we should never modify it as old resources will
+# not be available under the new namespace and ZFS Driver looks for all the resources
+# in the OPENEBS_NAMESPACE namespace passed as an env.
+
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: openebs