Description of problem (please be detailed as possible and provide log
snippests):
When running `noobaa status`, the CLI looks for the wrong DB PV name - it looks for the 4.6 PV instead of the 4.7 one.
Example:

20:38:58 - MainThread - /home/jenkins/workspace/qe-deploy-ocs-cluster/ocs-ci/ocs_ci/ocs/resources/mcg.py - ERROR - Error in noobaa status output- time="2020-12-17T20:38:58Z" level=info msg="❌ Not Found: PersistentVolumeClaim \"db-noobaa-db-0\"\n"
20:38:58 - MainThread - ocs_ci.utility.retry - WARNING - Cluster health is NOT OK, Retrying in 5 seconds...
20:39:03 - MainThread - ocs_ci.utility.utils - INFO - Executing command: /home/jenkins/workspace/qe-deploy-ocs-cluster/ocs-ci/data/mcg-cli status -n openshift-storage
20:39:05 - MainThread - ocs_ci.utility.utils - WARNING - Command stderr: time="2020-12-17T20:39:04Z" level=info msg="CLI version: 5.7.0\n"
time="2020-12-17T20:39:04Z" level=info msg="noobaa-image: quay.io/rhceph-dev/mcg-core@sha256:b1dadeda99d8be5aed1baaf3d6585bf5a5f8ce3b51856f01d352b224dc798170\n"
time="2020-12-17T20:39:04Z" level=info msg="operator-image: quay.io/rhceph-dev/mcg-operator@sha256:b35d0eba967246a90ea6f974cac1102698eafb485e2683d1fea5ec351c14c626\n"
time="2020-12-17T20:39:04Z" level=info msg="noobaa-db-image: registry.redhat.io/rhel8/postgresql-12@sha256:601d04709371f634e440bf949896a21ee5a36c402a2bb34bfff23960f4fb10ba\n"
time="2020-12-17T20:39:04Z" level=info msg="Namespace: openshift-storage"
time="2020-12-17T20:39:04Z" level=info
time="2020-12-17T20:39:04Z" level=info msg="CRD Status:"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: CustomResourceDefinition \"noobaas.noobaa.io\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: CustomResourceDefinition \"backingstores.noobaa.io\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: CustomResourceDefinition \"namespacestores.noobaa.io\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: CustomResourceDefinition \"bucketclasses.noobaa.io\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: CustomResourceDefinition \"objectbucketclaims.objectbucket.io\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: CustomResourceDefinition \"objectbuckets.objectbucket.io\"\n"
time="2020-12-17T20:39:04Z" level=info
time="2020-12-17T20:39:04Z" level=info msg="Operator Status:"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: Namespace \"openshift-storage\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: ServiceAccount \"noobaa\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: Role \"ocs-operator.v4.7.0-198.ci-noobaa-5498b64684\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: RoleBinding \"ocs-operator.v4.7.0-198.ci-noobaa-5498b64684\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: ClusterRole \"ocs-operator.v4.7.0-198.ci-7b44878bc7\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: ClusterRoleBinding \"ocs-operator.v4.7.0-198.ci-7b44878bc7\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: Deployment \"noobaa-operator\"\n"
time="2020-12-17T20:39:04Z" level=info
time="2020-12-17T20:39:04Z" level=info msg="System Status:"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: NooBaa \"noobaa\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: StatefulSet \"noobaa-core\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: Service \"noobaa-mgmt\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: Service \"s3\"\n"
time="2020-12-17T20:39:04Z" level=info msg="✅ Exists: Secret \"noobaa-db\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: StatefulSet \"noobaa-db-pg\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: Service \"noobaa-db-pg\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: Secret \"noobaa-server\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: Secret \"noobaa-operator\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: Secret \"noobaa-endpoints\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: Secret \"noobaa-admin\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: Secret \"noobaa-root-master-key\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: StorageClass \"openshift-storage.noobaa.io\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: BucketClass \"noobaa-default-bucket-class\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: Deployment \"noobaa-endpoint\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists: HorizontalPodAutoscaler \"noobaa-endpoint\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ (Optional) Exists: BackingStore \"noobaa-default-backing-store\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ (Optional) Exists: CredentialsRequest \"noobaa-aws-cloud-creds\"\n"
time="2020-12-17T20:39:05Z" level=info msg="⬛ (Optional) Not Found: CredentialsRequest \"noobaa-azure-cloud-creds\"\n"
time="2020-12-17T20:39:05Z" level=info msg="⬛ (Optional) Not Found: Secret \"noobaa-azure-container-creds\"\n"
time="2020-12-17T20:39:05Z" level=info msg="⬛ (Optional) Not Found: Secret \"noobaa-gcp-bucket-creds\"\n"
time="2020-12-17T20:39:05Z" level=info msg="⬛ (Optional) Not Found: CredentialsRequest \"noobaa-gcp-cloud-creds\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ (Optional) Exists: PrometheusRule \"noobaa-prometheus-rules\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ (Optional) Exists: ServiceMonitor \"noobaa-mgmt-service-monitor\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ (Optional) Exists: ServiceMonitor \"s3-service-monitor\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ (Optional) Exists: Route \"noobaa-mgmt\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ (Optional) Exists: Route \"s3\"\n"
time="2020-12-17T20:39:05Z" level=info msg="❌ Not Found: PersistentVolumeClaim \"db-noobaa-db-0\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ System Phase is \"Ready\"\n"
time="2020-12-17T20:39:05Z" level=info msg="✅ Exists:  \"noobaa-admin\"\n"


Version of all relevant components (if applicable):
CLI 5.7.0
ocs-operator.v4.7.0-198.ci

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

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

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

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
No

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

Steps to Reproduce:
1. Run `noobaa status`
2. Verify that the command finds the appropriate DB PV 

Actual results:
`noobaa status` fails

Expected results:
`noobaa status` passes successfully


Additional info: