Add e2e test case for issue 7725

[hollycai05]

Thank you for contributing to Velero!

Please add a summary of your change

Add e2e test case for issue 7725: make kopia repo cache place configurable

Does your change fix a particular issue?

Fixes #(issue)
#7725

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.

[hollycai05]

root@corgi-jumper:~/velero# REPO_TAG=main VERSION=main VELERO_IMAGE=upstream-dockerhub-virtual.packages.vcfd.broadcom.net/velero/velero:release-1.18-dev PLUGINS=upstream-dockerhub-virtual.packages.vcfd.broadcom.net/velero/velero-plugin-for-aws:release-1.14-dev RESTORE_HELPER_IMAGE=upstream-dockerhub-virtual.packages.vcfd.broadcom.net/velero/velero:release-1.18-dev ITEM_BLOCK_WORKER_COUNT=1 IMAGE_REGISTRY_PROXY=upstream-dockerhub-virtual.packages.vcfd.broadcom.net WORKER_OS=linux GINKGO_LABELS="NodeAgentConfig && CachePVC" UPGRADE_FROM_VELERO_VERSION= BSL_CONFIG=region=minio,s3ForcePathStyle=true,s3Url=http://10.192.1.130:9000 CREDS_FILE=$HOME/minio-credential BSL_BUCKET=default-bucket OBJECT_STORE_PROVIDER=aws CLOUD_PROVIDER=vsphere FEATURES=EnableCSI VERSION=release-1.18-dev SNAPSHOT_MOVE_DATA=true DISABLE_INFORMER_CACHE=true REGISTRY_CREDENTIAL_FILE=$HOME/.docker/config.json KIBISHII_DIRECTORY=$HOME/kibishii/kubernetes/yaml ITEM_BLOCK_WORKER_COUNT=1 WORKER_OS=linux make test-e2e


Backup 2026-03-04 09:52:05
velero cmd =/root/velero/test/../_output/bin/linux/amd64/velero create --namespace velero backup backup-cache-pvc-89983259 --include-namespaces cache-pvc-89983259-0 --snapshot-volumes=true --snapshot-move-data
Backup request "backup-cache-pvc-89983259" submitted successfully.
Run `velero backup describe backup-cache-pvc-89983259` or `velero backup logs backup-cache-pvc-89983259` for more details.
Waiting for backup to complete...
Destroy 2026-03-04 09:52:50
  STEP: Start to destroy namespace cache-pvc-89983259...... @ 03/04/26 09:52:50.947
[delete namespace cache-pvc-89983259-0]
/usr/local/bin/kubectl delete namespace cache-pvc-89983259-0
Output: namespace "cache-pvc-89983259-0" deleted

[/usr/local/bin/kubectl get ns /usr/bin/grep cache-pvc-89983259-0 /usr/bin/awk {print $1}]
kubectl get ns output:
[]
Namespace cache-pvc-89983259-0 was deleted
Restore 2026-03-04 09:54:17
velero cmd =/root/velero/test/../_output/bin/linux/amd64/velero create --namespace velero restore restore-cache-pvc-89983259 --from-backup backup-cache-pvc-89983259
Restore request "restore-cache-pvc-89983259" submitted successfully.
Run `velero restore describe restore-cache-pvc-89983259` or `velero restore logs restore-cache-pvc-89983259` for more details.
Start to verify restore data mover pod content.
Restore data mover pod content verification completed successfully.
Verify 2026-03-04 09:55:07
Finish run test 2026-03-04 09:55:07
  STEP: Clean namespace with prefix cache-pvc-89983259 after test @ 03/04/26 09:55:07.921
  STEP: Clean backups after test @ 03/04/26 09:55:07.934
Backup backup-cache-pvc-89983259 is going to be deleted...
velero cmd =/root/velero/test/../_output/bin/linux/amd64/velero --namespace velero delete backup backup-cache-pvc-89983259 --confirm
Request to delete backup "backup-cache-pvc-89983259" submitted successfully.
The backup will be fully deleted after all associated data (disk snapshots, backup files, restores) are removed.
• [215.540 seconds]
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[AfterSuite] 
/root/velero/test/e2e/e2e_suite_test.go:811
  STEP: Delete StorageClasses created by E2E @ 03/04/26 09:55:08.071
  STEP: Delete PriorityClasses created by E2E @ 03/04/26 09:55:08.078
  STEP: Delete VolumeSnapshotClass created by E2E @ 03/04/26 09:55:08.084
[delete -f ../testdata/volume-snapshot-class/vsphere.yaml --force=true]
  STEP: release test resources after testing @ 03/04/26 09:55:08.192
Velero uninstalled ⛵
[AfterSuite] PASSED [11.086 seconds]
------------------------------
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
[ReportAfterSuite] PASSED [0.007 seconds]
------------------------------

Ran 1 of 62 Specs in 247.537 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 61 Skipped
PASS

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.64%. Comparing base (8b55592) to head (b164899).
⚠️ Report is 15 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9567      +/-   ##
==========================================
- Coverage   60.65%   60.64%   -0.01%     
==========================================
  Files         386      387       +1     
  Lines       36477    36518      +41     
==========================================
+ Hits        22124    22146      +22     
- Misses      12771    12783      +12     
- Partials     1582     1589       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[blackpiglet]

  Error: test/e2e/nodeagentconfig/cache_pvc.go:225:2: ginkgo-linter: wrong length assertion. Consider using `Expect(restorePodList.Items).ToNot(BeEmpty())` instead (ginkgolinter)
  	Expect(len(restorePodList.Items)).To(BeNumerically(">", 0))

Please address the linter issue.