e2e: run the FSBackup backup deletion case on kind under CSI (#10764)

* e2e: run the FSBackup backup deletion case on kind under CSI

The Snapshot variant of this case has run in the CSI job since #10658.
Its FSBackup twin is in no matrix row at all, so the backup deletion
path has never been exercised on kind with file system backup.

That exclusion predates file system backup working on kind. #10680
established that it does, once Kibishii's PVs come from the kind-csi
overlay rather than rancher.io/local-path, because isHostPathVolume
stops matching a PV carrying pv.Spec.CSI.

Run on kind with EnableCSI and Kibishii at the commit this workflow
pins:

  Backups && Deletion && FSBackup   Ran 1 of 70 Specs in 502.394 seconds

Worth being precise about what that shows. The case backs up with
--default-volumes-to-fs-backup, deletes the backup, and verifies it is
gone from object storage. It does not query PodVolumeBackups or verify
restored data, so unlike the cases in #10680 the log does not contain
PVB names. What this run demonstrates is that an FSBackup-flagged backup
completes and deletes cleanly on kind, which is the path the case is
about.

The row selects only this one case; Backups && Deletion && Snapshot
keeps its own row.

Signed-off-by: krishhna24 <krishhnatupedev@gmail.com>

* Add changelog for #10764

Signed-off-by: krishhna24 <krishhnatupedev@gmail.com>

---------

Signed-off-by: krishhna24 <krishhnatupedev@gmail.com>

.github/workflows/e2e-test-kind.yaml

@@ -215,7 +215,8 @@ jobs:
               \"Backups && Deletion && Snapshot\", \
               \"NamespaceMapping && Snapshot\", \
               \"Basic && FSBackup\", \
-              \"BSL && Deletion && Snapshot\"\
+              \"BSL && Deletion && Snapshot\", \
+              \"Backups && Deletion && FSBackup\"\
             ]}" >> $GITHUB_OUTPUT
 
   # Run E2E test against all Kubernetes versions on kind

changelogs/unreleased/10764-krishhna24

@@ -0,0 +1 @@
+Run the FSBackup backup deletion case on kind in CI when CSI is enabled