[Woo POS][Modularization] Remove ServiceLocator.analytics dependency from POS code

[staskus]

Description

More context: pdfdoF-7It-p2
Next PR: #15956

This is the start of the POS modularization work. For now, I'm merging everything into a development branch since things can still change a lot along the way and I don't want to be affecting trunk.

The goal of this PR is to remove one of the larger dependencies between POS and the main app code -Analytics through ServiceLocator. Also, create a platform on which to build further refactorings:

1. Created PointOfSale and PointOfSaleTests target modules
2. Defined POSAnalyticsProviding protocol within the PointOfSaleModule
3. Created POSAnalyticsAdapter within the Woo app code that implements POSAnalyticsProviding to be injected into POS in the entry point
4. Moved WooAnalyticsStat and WooAnalyticsEvent to WooFoundation to be reused between different modules.
5. Moved POS-related analytic files to PointOfSale module. I also moved some models and entities that were used within analytics files to avoid changing things too much.
6. Replaced usage of ServiceLocator.analytics with injected or environment version of POSAnalyticsProviding

Intermediate changes:

• While refactoring is ongoing, I need to make some PointOfSale module types public to be used within the Woo app, I will turn them back to internal when refactoring is complete
• For the same reason, I added a global import of PointOfSale to avoid importing it into tens or hundreds of files within the Woo app. In the end, we should only have one import PointOfSale in the entry point (POSTabCoordinator)

Steps to reproduce

Review a general approach. Thorough testing is not necessary since it's not targeting the trunk.

• CI should succeed
• POS should launch
• POS events should be tracked

Testing information

Tested on iPad 18.5 simulator, iPad Air M2 26 device

---

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

[dangermattic]

	3 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).
⚠️	View files have been modified, but no screenshot or video is included in the pull request. Consider adding some for clarity.
⚠️	This PR is larger than 300 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.

	1 Message
📖	This PR contains changes to Tracks-related logic. Please ensure (author and reviewer) the following are completed: The tracks events must be validated in the Tracks system. Verify the internal Tracks spreadsheet has also been updated. Please consider registering any new events. The PR must be assigned the category: tracks label.

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	pr15955-418d8a7
	Version	22.9
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	418d8a7
	Installation URL	0n4o8bilv09c0

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

[jaclync]

Nice work! Tested making a cash payment in POS and the events were tracked and sent remotely as before. Keeping all changes in a development branch makes sense, maybe the dev branch can be merged to trunk by the end of the week / early next week since we might resume POS work after the HACK Week.

[staskus]

@jaclync I appreciate the review! 🙇

I know it's complicated to review since there are a lot of changes, and the future PRs make further changes on top of that. I have an idea in my mind of how this should be executed, but I discover new things along the way as I change plans.

I will incorporate your comments in the next PR #15956 that I have.