Consider testing data access during the

[leafty]

Reference: https://github.com/container-storage-interface/spec/blob/master/spec.md#createvolume

Consider testing data access (e.g. rclone lsf remote:<subpath>) during the CreateVolume request handling and see if failing to create the volume with error 16 UNAUTHENTICATED avoids Kubernetes continuing to try to mount a volume with NodePublishVolume requests.

Context: when a volume is requested and the corresponding credentials are incorrect, we (csi-rclone) keep trying to mount it into the corresponding pod.