Description of problem:

Re-enabling the ArgoCD application for ZTP after ACM restore on secondary Hub cluster triggered the redeployment of all the managed clusters.

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

ACM 2.8.5

Steps to Reproduce:

1. DEVHUB01 was backing up to an S3 bucket.
2. DEVHUB02 was restoring using the "Restoring passive resources while checking for backups" method from the documentation.
3. DEVHUB01 was shutdown.
4. The restore configuration on DEVHUB02 was edited so the managed cluster resources would be restored by changing `.spec. veleroManagedClustersBackupName` from `skip` to `latest`.
5. We validated that managed clusters has been restored based on resources present on DEVHUB02 and resources managed by templated policies which referenced the hub cluster name now contained `devhub02` instead of `devhub01`.
6. An additional restore was then created on DEVHUB02 so that it would synchronized the git repo secret and allow OpenShift GitOps to synchronize the ZTP repo which contains the SiteConfigs for the managed clusters.

Actual results:

All managed clusters redeployed after restore.

Expected results:

All managed clusters should work properly without redeployment and be manageable by the restore Hub cluster.

Additional info: