Remove VAST CSI Driver 2.1.x or 2.0.x

After removal of VAST CSI Driver 2.1.x or 2.0.x, the existing containers will continue to run with the volumes provisioned by the removed VAST CSI Driver.

Remove all VAST storage classes:
```
kubectl delete sc vastdata-filesystem
```

Remove the VAST CSI driver:

kubectl delete csidriver csi.vastdata.com

Remove the VAST namespace:
Caution
If your PVCs are in the same namespace as the driver, take preliminary action to prevent deletion of the PVCs as a result of the namespace deletion.
```
kubectl delete all --all -n vast-csi
```

Remove the VAST ServiceAccounts:

kubectl delete sa csi-vast-controller-sa -n vast-csi
kubectl delete sa csi-vast-node-sa -n vast-csi

Remove the VAST Secret:

kubectl delete secret csi-vast-mgmt -n vast-csi

Remove the VAST ClusterRole:

kubectl delete ClusterRole csi-vast-attacher-role
kubectl delete ClusterRole csi-vast-provisioner-role

Remove the VAST ClusterRoleBinding:

kubectl delete ClusterRoleBinding csi-resizer-role
kubectl delete ClusterRoleBinding csi-vast-attacher-binding
kubectl delete ClusterRoleBinding csi-vast-provisioner-binding

Remove the VAST VolumeSnapshotClass:

kubectl delete VolumeSnapshotClass vastdata-snapshot