feat: out-order-ipex

[jimcase]

Description

There are scenarios where we will receive notifications out of order. We add them to the failed queue so they get re-processed.

However, in the case of group IPEX, we may receive notifications that related to deleted notifications. For example, once the threshold is met when accepting a credential, the notification from the issuer is deleted.

There is a timing gap where the long running operation for accepting completes first, the notification is deleted, and then the notification is received to indicate that the other member has accepted.

We need to handle this better.

Error: OUT_OF_ORDER_NOTIFICATION

Checklist before requesting a review

Issue ticket number and link

• This PR has a valid ticket number or issue: [link]

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