chore: remove code from WireDomain package - WPB-14598

[caldrian]

WPB-14598 [iOS] Add shared backup library as a dependency

Issue

This PR removes the more or less redundant WireDomain package, but keeps the WireDomain Xcode project.

Testing

Describe how to test.

Optional: attachments like images, videos, etc.

---

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

    6 files    502 suites   4m 29s ⏱️
3 307 tests 3 148 ✅ 28 💤 131 ❌
3 317 runs  3 159 ✅ 28 💤 130 ❌

For more details on these failures, see this check.

Results for commit af187e2.

♻️ This comment has been updated with latest results.

[samwyndham]

Hey @caldrian

In the current PR I'm working on I add a new target to WireDomain SPM.

Basically for the new syncing we duplicate many models from WireDomain just for the purpose of decoding/encoding into data. This is to prevent an innocent change to something like QualifiedID such as the rename of property from breaking the decoding of stored UpdateEvents. I would like to keep these models in a separate target from the main WireDomain target because the public API is tiny and I don't want to confuse things in that target. I can certainly move my code elsewhere but can we wait until next week before merging this PR to discuss a bit further. I don't really have time today to look into it

[caldrian]

Hey @caldrian

In the current PR I'm working on I add a new target to WireDomain SPM.

Basically for the new syncing we duplicate many models from WireDomain just for the purpose of decoding/encoding into data. This is to prevent an innocent change to something like QualifiedID such as the rename of property from breaking the decoding of stored UpdateEvents. I would like to keep these models in a separate target from the main WireDomain target because the public API is tiny and I don't want to confuse things in that target. I can certainly move my code elsewhere but can we wait until next week before merging this PR to discuss a bit further. I don't really have time today to look into it

Reverted deleting the target.

[samwyndham]

Nice work 🧹

[jullianm]

@caldrian question: I assume we can't solely keep the Swift package and remove the Xcode project because it relies on other Xcode framework like WireDataModel and WireTransport, right?

thought: My concern is that we gradually adopt Swift packages for new code, I wonder is there's a possibility to do the other way around : keep the WireDomain package, remove the Xcode framework and embed legacy frameworks into Swift packages (as binaryTarget?) that WireDomain package could use. (probably out of scope of this PR as it would require much more effort, just a thought)