fix: sub conversation epoch verification [WPB-15647] 🍒

[github-actions]

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

• fix: sub conversation epoch verification [WPB-15647] #3244

Original PR description:

---

WPB-15647 [Android] epoch check for sub conversations is verifying the main conversation

---

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

The previous implementation did not handle epoch verification for sub-conversations. As a result, the verification process always checked the parent conversation's epoch, leading to incorrect behavior when the sub-conversation epoch was out of sync while the parent conversation's epoch remained valid.

Causes

1. Lack of Sub-Conversation Handling: Sub-conversations were not considered during epoch verification.
2. Missing Models and Logic: There were no models or logic in place to support sub-conversation-specific checks.
3. Incorrect Parent Conversation Focus: Epoch verification defaulted to the parent conversation, ignoring sub-conversations entirely.

Solutions

1. Added verifySubConversationEpoch:

   • A dedicated method to verify epochs for sub-conversations, ensuring accurate context for verification.

2. Sub-Conversation Repository Arrangement:

   • Created SubconversationRepositoryArrangement to mock and test sub-conversation-related methods efficiently.

3. Introduced Sub-Conversation Models:

   • Added models in the logic module to handle sub-conversations as first-class entities.

4. Updated Epoch Verification Logic:

   • Refactored NewMessageEventHandler to call verifySubConversationEpoch when a subConversationId is provided.

5. Added Comprehensive Tests:

   • Verified that fetchConversation is not called when a subConversationId is present.
   • Ensured correct behavior for valid epochs, stale epochs, and failures.

[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