The MultiClusterObservability global resource is now backed up with the acm-resources-schedule, which contains all resources that are being moved to the passive cluster, before the cluster become primary

As I was investigating the PV backup support, I realized that the MultiClusterObservability resource once moved on the restore hub creates all obs resources using the backed secrets and configmaps; as a result it creates PV and PVClaims

I don't think we want to do that; the passive and still active hub point to the same PV

I suggest adding this label to the  MultiClusterObservability CR , which makes the resource restored only at passive activation time

```
labels:
cluster.open-cluster-management.io/backup: cluster-activation
```

More details here https://github.com/stolostron/cluster-backup-operator#resources-restored-at-managed-clusters-activation-time