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

When NamespaceStore's target bucket is deleted and the NamespaceStore is used in a Namespace bucket, alerts NooBaaNamespaceBucketErrorState and NooBaaNamespaceResourceErrorState are not triggered.

This was found via automated test test_noobaa_ns_bucket.
Jenkins test run with logs: https://ocs4-jenkins-csb-odf-qe.apps.ocp-c1.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/10581

Version of all relevant components (if applicable):
OCS 4.15.0-144

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)?

3

Can this issue reproducible?

Yes

Can this issue reproduce from the UI?

yes

If this is a regression, please provide more details to justify this:
issue will be logged 2nd time, after the bz 1986444 and bz 2184375

Steps to Reproduce:
1. Create a Namespace bucket with one Namespacestore
2. Delete target bucket used by the Namespacestore
3. Check alerts for 12 minutes

(issue reproduced manually)

Actual results:
Alerts NooBaaNamespaceBucketErrorState and NooBaaNamespaceResourceErrorState are not present.

Expected results:
If NamespaceStore is unhealthy then bucket that uses the NamespaceStore is unhealthy too and proper alerts are raised.