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

Using the noobaa CLI to delete a bucketclass or an OBC that doesn't exist does not result in an error as expected:

```
$ noobaa bucketclass delete non-existant-bc | grep -i err || echo "No errors "
No errors

$ mcg-cli obc delete non-existant-obc | grep -i err || echo "No errors "
No errors
```

Version of all relevant components (if applicable):
------------------------------------------------------------------------
ODF: 4.17.0-108
noobaa core: 5.17.0-b1c72eb
noobaa operator: 5.17.0-890badeb954acea07365f204e20f9443970dc560
noobaa cli: 5.17.0

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
------------------------------------------------------------------------
Mildly - the issue here is mainly inconsistency since we do get an error when attempting to delete non-existent Backingstores or Namespacestores:

$ mcg-cli backingstore delete non-existent-backingstore
...
...
ERRO[0004] ⚠️  RPC: pool.read_pool() Response Error: Code=NO_SUCH_POOL Message=No such pool: non-existent-backingstore 

$ mcg-cli namespacestore delete non-existent-namespacestore
...
...
ERRO[0004] ⚠️  RPC: pool.read_namespace_resource() Response Error: Code=NO_SUCH_NAMESPACE_RESOURCE Message=No such namespace resource: non-existent-namespacestore

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

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?
------------------------------------------------------------------------
N/A

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

Additional info:
------------------------------------------------------------------------
must-gather logs:
https://url.corp.redhat.com/cf979e0