Description of problem:

When the restore passive operation is being used, when the activation data is restored by updating the veleroManagedClustersBackupName: latest on this resource, the activation resources might not be restored.

This is because the activation restore is trying to use the same velero restore as the sync restore, unless a new backup has been created when the activation is started.

https://github.com/stolostron/cluster-backup-operator/blob/main/config/samples/cluster_v1beta1_restore_passive_sync.yaml

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

How reproducible:

Always with the steps below

Steps to Reproduce:

1. Backup hub resources and create at least one resource R with this label : cluster.open-cluster-management.io/backup: cluster-activation. This resource should be restored at activation time.  
2. On a new hub, run a restore passive with sync operation , using this sample https://github.com/stolostron/cluster-backup-operator/blob/main/config/samples/cluster_v1beta1_restore_passive_sync.yaml
3. Verify that the resource are restored , with the exception of this R resource. This is the expected output
4. Without waiting for a new backup to be generated, run the activation step : on the Restore resource created at step 2, set veleroManagedClustersBackupName: latest
    
5. This should result in restoring resource R. This is not happening because no new backup was created, the restore files names are generated using the backup name, so a new restore will not be executed 

Actual results:

R is not restored at step 5

Expected results:

R should be restored at step 5

Additional info: