refactor: process federation delete event - WPB-10188

[jullianm]

WPB-10188 [iOS] Process FederationDeleteEvent

Key Points

This PR is part of the quick sync refactoring plan and is related to processing the multiple events we receive from the backend or the push channel.

Specifically, this PR is about porting the existing implementation of the FederationDeleteEventProcessor event.

Legacy code was using a FederationTerminationManager part of WireRequestStrategy framework to manage the storage logic.

federationTerminationManager.handleFederationTerminationWith(payload.domain)

To avoid using this internal dependency, we now directly perform the storage logic operations in our dedicated ConnectionRepository object.

Note: The following ongoing PR here was merged into this one as they are closely related.

Testing

UTs cover the following use cases, ensuring that:

• a 1:1 conversation is marked as read-only.
• pending connections requests are ignored.
• sent connection requests are cancelled.
• connections for connected users are removed.
• selfUser is removed from conversation hosted by defederated domain.
• it removes a user from a conversation hosted by self user domain.
• it removes selfUser and another user from a conversation hosted by another domain.

Checklist

• Title contains a reference JIRA issue number like [WPB-XXX].
• Description is filled and free of optional paragraphs.
• Adds/updates automated tests.

---

UI accessibility checklist

If your PR includes UI changes, please utilize this checklist:

• Make sure you use the API for UI elements that support large fonts.
• All colors are taken from WireDesign.ColorTheme or constructed using WireDesign.BaseColorPalette.
• New UI elements have Accessibility strings for VoiceOver.

[github-actions]

Test Results

233 tests   233 ✅  6s ⏱️
 38 suites    0 💤
  2 files      0 ❌

Results for commit 18662f1.

♻️ This comment has been updated with latest results.

[netbe]

should we close #1900 then? @jullianm
the rest looks ok apart from swiftlint warnings

[jullianm]

@netbe yep I closed the other PR since changes are already part of this PR