vSphere CSI storage policy in wallaby

[vxav]

The CSI fails to provision storage because the csi chart defaults to a vsan storage policy. This fails if the available datastore has no storage policy applied (e.g. traditional storage array).

No vSAN datastores found for vCenter \"160.100.1.65\

failed to retrieve tags for category \"cns.vmware.topology-preferred-datastores\" in vCenter \"160.100.1.65\

No compatible datastore found for storagePolicy

One fix is to remove the storagePolicy section of the storage class. Meaning it will pick whatever datastore is available. This is fine as long as there's only one.
https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/3.0/vmware-vsphere-csp-getting-started/GUID-4E5F8F65-8845-44EE-9485-426186A5E546.html

When a storage policy is not specified in the StorageClass, the vSphere Container Storage Plug-in looks for a shared, accessible datastore that can be accessed by all nodes in the Kubernetes cluster.

tl,dr: We need to be able to not specify a storage policy in the storage class.
https://github.com/giantswarm/cloud-provider-vsphere-app/blob/main/config/vsphere-csi-driver/overwrites/values.yaml#L11

[vxav]

Done in giantswarm/cluster-vsphere#264