Move users to a new WordPressCore module

[crazytonyli]

This PR is not buildable yet (pending a wordpress-rs alpha release) Update: this PR now uses the latest wordpress-rs alpha version. But the changes are fairly simple. I thought we could get the changes reviewed while waiting for the alpha release.

This PR moves the non-UI part of self-hosted user management and some foundational things it uses to a new module WordPresCore, which includes strict concurrency checks. The new module will include components communicating with WordPress sites via REST API in WordPress core (hence the name). I'm open to suggestions of better module names.

Regression Notes

1. Potential unintended areas of impact

2. What I did to test those areas of impact (or what existing automated tests I relied on)

3. What automated tests I added (or what prevented me from doing so)

PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding unit tests for my changes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Testing checklist:

• WordPress.com sites and self-hosted Jetpack sites.
• Portrait and landscape orientations.
• Light and dark modes.
• Fonts: Larger, smaller and bold text.
• High contrast.
• VoiceOver.
• Languages with large words or with letters/accents not frequently used in English.
• Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
• iPhone and iPad.
• Multi-tasking: Split view and Slide over. (iPad)

[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).
⚠️	View files have been modified, but no screenshot or video is included in the pull request. Consider adding some for clarity.

Generated by 🚫 Danger

[kean]

This PR moves the non-UI part of self-hosted user management and some foundational things it uses to a new module WordPresCore, which includes strict concurrency checks. The new module will include components communicating with WordPress sites via REST API in WordPress core (hence the name). I'm open to suggestions of better module names.

Any plans for the Core Data entities and the related services?

The name seems OK.

[jkmassel]

Any plans for the Core Data entities and the related services?

A Core Data-based DataStore would be pretty easy to implement – that could be part of this module, or could be implemented elsewhere. This PR is a good start from migrating away from Core Data where it's not needed

[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	pr24014-9ec4ada
	Version	25.7
	Bundle ID	org.wordpress.alpha
	Commit	9ec4ada
	App Center Build	WPiOS - One-Offs #11412

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	pr24014-9ec4ada
	Version	25.7
	Bundle ID	com.jetpack.alpha
	Commit	9ec4ada
	App Center Build	jetpack-installable-builds #10444

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

[kean]

I can see how this was ambiguous.