Description of problem (please be detailed as possible and provide log
snippests):

[DR] ramen-hub-operator and ramen-dr-cluster-operator Pod lables should be based in deployment name

Version of all relevant components (if applicable):

odf-operator.v4.9.0-138.ci

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Deploy 2 DR cluster
2. Check pod label for ramen pods
3. 


Actual results:
# Managed cluster
oc get pods -n openshift-operators --show-labels 
NAME                                         READY   STATUS    RESTARTS   AGE     LABELS
ramen-dr-cluster-operator-588fb65c78-rjbzv   2/2     Running   0          5d19h   control-plane=controller-manager,pod-template-hash=588fb65c78

# Hub
oc get pods -n openshift-operators --show-labels
NAME                                        READY   STATUS    RESTARTS        AGE     LABELS
ramen-hub-operator-56fdb57f46-qlkqt         2/2     Running   1 (3d23h ago)   5d19h   control-plane=controller-manager,pod-template-hash=56fdb57f46


Expected results:


Additional info: