feat(core): marking notification as read when deleting distributed reliability

[Sotatek-TungNguyen2a]

Description

We mark notifications as read once we have deleted them, or we are done processing them if they are not user facing.

A notification can only be marked once, or it will return 404.

It’s possible that we mark it as read, and crash before deleting the notification in the local database of the wallet.

When we try to delete again, we will hit this 404 error.

Checklist before requesting a review

Issue ticket number and link

• This PR has a valid ticket number or issue: 1597

Testing & Validation

• This PR has been tested/validated in IOS, Android and browser.
• The code has been tested locally with test coverage match expectations.
• Added new Unit/Component testing (if relevant).

Security

• No secrets are being committed (i.e. credentials, PII)
• This PR does not have any significant security implications

Code Review

• There is no unused functionality or blocks of commented out code (otherwise, please explain below)
• In addition to this PR, all relevant documentation (e.g. Confluence) and architecture diagrams (e.g. Miro) were updated