Migrate from CocoaPods to SwiftPM in Modules

[mokagio]

Description

See https://linear.app/a8c/issue/AINFRA-216 and its sub-issues.

This PR uses the set up established by #15654 to move all pods to SwiftPM, except for:

• WordPressShared and WordPressUI, which we'll fold into the codebase soon
• WPMediaPicker, see Migrate WPMediaPicker from Cocoapods by folding the source #15660
• Wormholy, which currently does not support SwiftPM, see Showcase Wormholy 1.7.0 SwiftPM issue #15663

Steps to reproduce && Testing information

See green CI and that the prototype build for a spin.

Screenshots

---

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[dangermattic]

	1 Warning
⚠️	This PR is larger than 300 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 WooCommerce iOS Prototype by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce iOS Prototype
	Build Number	30037
	Version	PR #15658
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	dcabc22
	Installation URL	3u4gfc8o6rlh8

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

[mokagio]

Most of the framework projects no longer have pods target, therefore a lot of CocoaPods plumbing has been removed from their project files.

But keep in mind, the project files will soon disappear, too, with the move of the frameworks to packages.

[mokagio]

I commented in #15654 that I'm surprised we still have the Package.resolved in the workspace when there are no longer package dependencies there, only the internal Modules package.

Xcode keeps generating this file, so there must be something still configured for it in there.

I'm delaying tackling this inconsistency till after having moved everything to SwiftPM. It should be simpler to diagnose then, with less moving parts in Xcode itself.

[mokagio]

Some import required tweaking after the move to SwiftPM. I haven't investigate, but my guess is that the packaging and linking is slightly different and therefore some headers that were implicitly part of the linkage no longer are. As you can see, the footprint is small.

[staskus]

The project continues to work as before 👍