Unlock a locked repository using the restic backup tool in RHOCP4

Issue

• Velero pod complains about locked repository.

  time="XXXXX" level=warning msg="error pruning repository" error="error running command=restic prune --repo=s3:http://minio-veleroXXXXX--password-file=/tmp/credentials/oadpXXXXX --cache-dir=/scratch/.cache/restic, stdout=, stderr=unable to create lock in backend: repository is already locked exclusively by PID XXXXX on velero-b666455f9-XXXXX was created at XXXXX  `unlock` command can be used to remove stale locks\n: exit status 1" error.file="/remote-source/velero/app/pkg/restic/repository_manager.go:296" error.function="github.com/vmware-tanzu/velero/pkg/restic.(*repositoryManager).exec" logSource="/remote-source/velero/app/pkg/controller/restic_repository_controller.go:198" resticRepo=oadp-operator/XXXXX