Description of problem:

related to https://issues.redhat.com/browse/ACM-9632

If a configMap with 
cluster.open-cluster-management.io/backup-pvc label is found during a restore operation, the backup operator must wait for the PVC to be created ( by the pvc policy , which also restores the snapshot using a volsync DestinationReplication) , before creating activation resources. This allow the PVC to be restored before the app using the pvc uses the volume.
The issue reported here : The operator waits for the PVC but if, during the wait, another credentials backup is created by the primary hub , the new credential is picked up and because the wait stops.
The wait should not resume if only credential backups have been restored.

Version-Release number of selected component (if applicable):

How reproducible:

Always

Steps to Reproduce:

1. On the primary hub ( have the pv policy installed ) then set the 
   cluster.open-cluster-management.io/backup-hub-pvc label on a PVC so the configmap with  
   cluster.open-cluster-management.io/backup-pvc is created and backed up
2. Run an acm backup schedule on the restore hub to make sure the data is backed up
3. Go to the restore hub:
   1. On the restore hub remove the pvc policies so that after a restore you get into the wait stage
   2. Run a restore all operation
   3. You should see the Restore status saying : wait for PVC to be created.. ; and shows the. credentials file restored 
4. Now go back on the backup hub and trigger a new backup ( delete one of the velero schedules , this should trigger that )
5. Go back to the restore hub and wait until the new backup is sync up and picked up by the restore op ( which uses latest as the option to restore )
6. You should see at some point in the acm restore status that the new credentials backup was restored ( you can also check that you see the velero restore resource )
7. Notice the wait is resumed and all resources are restored, even though the PVC was not created yet 

Actual results:

1. Notice the wait is resumed and all resources are restored, even though the PVC was not created yet 

Expected results:

Step 7 should not happen; the restore should still say wait until the PVC is created, even if a second credentials backup was restored.