fix: suppress buffer error for mls decrypt transaction [WPB-16233] 🍒

[github-actions]

This PR was automatically cherry-picked based on the following PR:

• fix: suppress buffer error for mls decrypt transaction [WPB-16233] #3305

Original PR description:

---

WPB-16233 [Android] Catch and suppress buffer errors inside transaction

---

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

Issues

• When receiving out-of-order commits (e.g., when a client is missing a preceding commit), the MLS client was throwing a BufferedFutureMessage exception instead of buffering and persisting the message.
• This led to transactions always rolling back and no buffered messages actually being saved.

Causes

• The code did not properly detect or handle MlsException.BufferedFutureMessage (wrapped in CoreCryptoException.Mls) within the transactional decryption flow.
• As a result, any out-of-order commit triggered a rollback, preventing buffering logic from persisting the messages that should be processed later.

Solutions

• Updated the decryptMessage flow to wrap calls in a transactional API and specifically catch BufferedFutureMessage exceptions, allowing the transaction to commit and the message to be buffered rather than rolled back.
• Added tests verifying that out-of-order commits no longer throw exceptions and that previously buffered commits are eventually flushed once the missing epoch is processed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud