Description of problem (please be detailed as possible and provide log
snippests):
In BZ Bug 2265109 - NooBaaNamespaceBucketErrorState and NooBaaNamespaceResourceErrorState are not triggered when namespacestore's target bucket is deleted the fix was in PR #7846 (https://github.com/noobaa/noobaa-core/pull/7846).

This fix revealed a bug that we had in the code - when using the AWS SDK v3 the error properties were changed to uppercase, so instead of err.code it was err.Code. We had a function `check_error_code`, but if the catch is using `throw err` and the caller is looking for `err.code` - it will not find it.
Hence whenever we use the `noobaa_s3_client` and in the catch clause we have `throw err` we need to add the function `fix_error_object` so we will have the `code` property.

Version of all relevant components (if applicable):
4.15

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

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.
2.
3.

Actual results:

Expected results:

Additional info: