Convert WordPressData from Swift package to Xcode target

[mokagio]

To much Objective-C code using logic implemented elsewhere in Swift for us to be able to move the files in two separate Objective-C- and Swift- only packages.

Refer to #24166 as an experiment for this that shows the various build failure that even a partial attempt at moving some files results in.

---

Part of #24165

[dangermattic]

	2 Warnings
⚠️	Modules/Package.swift was changed without updating its corresponding Package.resolved. Please resolve the Swift packages as appropriate to your project setup (e.g. in Xcode or by running swift package resolve).
⚠️	This PR is larger than 500 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.

	App Name	WordPress Alpha
	Configuration	Release-Alpha
	Build Number	pr24194-4396c99
	Version	25.8
	Bundle ID	org.wordpress.alpha
	Commit	4396c99
	App Center Build	WPiOS - One-Offs #11651

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.

	App Name	Jetpack Alpha
	Configuration	Release-Alpha
	Build Number	pr24194-4396c99
	Version	25.8
	Bundle ID	com.jetpack.alpha
	Commit	4396c99
	App Center Build	jetpack-installable-builds #10680

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

[kean]

Is there something in particular worth reviewing?
Is this what we are going to go for, or are you planning to continue working towards making in a SwiftPM package? It will help to have it as an Xcode target (code completion should be better), but it will prevent it from using it from other SwiftPM packages.

[mokagio]

Closing in favor of #24242 , for now at least.

Sorry @kean I had missed your comment...

Is this what we are going to go for, or are you planning to continue working towards making in a SwiftPM package? It will help to have it as an Xcode target (code completion should be better), but it will prevent it from using it from other SwiftPM packages.

The work I've been doing in #24242 is at the target level. My hope is for the target to be a small intermediate step.

First, eradicate all the dependencies between what is clearly model code and the rest of the app. To do so, it helps to not have to worry about Objective-C using code defined in Swift itself built on top of Objective-C code. This circular dependency makes moving the code out too. I've been working on it for days and I'm still not done...

Once all the code is in WordPressData, and we can work on the target in isolation and with unit tests, restructuring to remove the circular dependencies, or simply rewriting all in Swift should be much faster.

I'm 100% on board with the Swift package being the desired end state.