Triggering snapshots when Volume Snapshots are not enabled in K8s returns a vague error.

[iamjoemccormick]

If a user doesn't go through the steps to enable volume snapshots on their Kubernetes cluster before attempting to trigger a snapshot, a vague 404 error will be returned from the Kubernetes API server because "API Objects VolumeSnapshot, VolumeSnapshotContent, and VolumeSnapshotClass are CRDs and not part of the core API".

To improve the user experience we should handle this error and return a message suggesting the user double check they went through the prerequisite tasks needed to enable VolumeSnapshots and link to the Trident documentation.

[iamjoemccormick]

While resolving this we should take the opportunity to cleanup a few related issues.

Currently functions like deleting a JupyterLab workspace result in a 404 error on the step where we try to cleanup any volume snapshots. This is because there are some scenarios where a user may not be using volume snapshots, so they didn't go through the steps to enable the feature. So in general we should make sure whenever we interact with the K8s API we account for the following scenarios:

• A K8s cluster without Volume Snapshots enabled.
• A K8s cluster with Volume Snapshots enabled but no snapshots for the ONTAP or BeeGFS PVC used to back the JupyterLab workspace.

Then for any functions that don't require snapshot functionality don't return an error and perhaps log an informational notice along the lines of "VolumeSnapshots are not enabled (skipping)".