fix csi data mover cleanup to remove orphaned VolumeSnapshotContent when DataUpload creation fails

[samay43]

summary of change

When CSI snapshot data movement is enabled, createDataUpload can fail after the VolumeSnapshot has been created but before the CSI snapshot controller has bound it to a VolumeSnapshotContent (i.e. before Status.BoundVolumeSnapshotContentName
is populated). In that window, CleanupVolumeSnapshot skipped patching the VolumeSnapshotContent's DeletionPolicy, deleted only the VolumeSnapshot, and left a Retain-policy VolumeSnapshotContent (and its underlying provider snapshot)
orphaned.
This adds a fallback: when Status.BoundVolumeSnapshotContentName is not yet set,
CleanupVolumeSnapshot now lists VolumeSnapshotContents and matches on Spec.VolumeSnapshotRef, which is populated at content-creation time regardless of the VolumeSnapshot's status. This ensures the orphaned content still gets its
deletion policy patched to Delete. Verified: go build ./... passes cleanly, and all existing plus new tests in
pkg/util/csi and pkg/backup/actions/csi pass.

fixed issue

Fixes #10287

Please indicate you've done the following:

• Accepted the DCO. Commits without the DCO will delay acceptance.
• Created a changelog file (make new-changelog) or comment /kind changelog-not-required on this PR.
• Updated the corresponding documentation in site/content/docs/main.

[netlify]

👷 Deploy request for velero pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	2440406

[codecov]

Codecov Report

❌ Patch coverage is 70.00000% with 6 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
pkg/util/csi/volume_snapshot.go	70.00%	3 Missing and 3 partials ⚠️

📢 Thoughts on this report? Let us know!