Storage tests failing in no-capabilities job

The no-capabilities job is currently failing because of some storage tests that seemingly can't pass when all optional capabilities are disabled.  See the results in:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.13-e2e-aws-ovn-no-capabilities/1628034290317004800

There was a previous attempt[1] to filter out the storage tests that can't pass in this environment, but it seems like some were missed.  The remaining failures (7 or so) need to be evaluated to determine if the tests should also be skipped in the no-caps job, or if the tests themselves should be modified to tolerate the no-caps cluster.

[1] https://github.com/openshift/origin/pull/27654 

Failing tests:

[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent) [Suite:openshift/conformance/parallel] [Suite:k8s]

[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Ephemeral Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral) [Suite:openshift/conformance/parallel] [Suite:k8s]

[sig-storage] Mounted volume expand [Feature:StorageProvider] Should verify mounted devices can be resized [Suite:openshift/conformance/parallel] [Suite:k8s]

[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Ephemeral Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works, check deletion (ephemeral) [Suite:openshift/conformance/parallel] [Suite:k8s]

[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned Snapshot (delete policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent) [Suite:openshift/conformance/parallel] [Suite:k8s]

[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Pre-provisioned Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent) [Suite:openshift/conformance/parallel] [Suite:k8s]

[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic Snapshot (retain policy)] snapshottable[Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent) [Suite:openshift/conformance/parallel] [Suite:k8s]

For most(but not all) of the tests the failure seems to be:
{  fail [k8s.io/kubernetes@v1.25.0/test/e2e/storage/framework/snapshot_resource.go:65]: Feb 21 14:54:23.209: the server could not find the requested resource
Ginkgo exit error 1: exit with code 1}

So probably there's a resource type that's not being registered when the storage cap is disabled, which these tests rely on.  So again, either the tests need to changed to be able to work w/o that resource, or the tests should be skipped in a no-caps cluster because they are not relevant.

v4.13

Always

1. Run the no-caps job, or bring up a cluster with capabilitySet: None
2. run the storage tests in question

tests fail

tests pass or are skipped