Centralize commands to config Sim in UI tests in aggregate target

[mokagio]

By moving them in an aggregate target on which the UI tests targets depend, we DRY the setup as well as making the existence of this capability more visible (in the targets list instead of buried in the build phases).

Having the commands in a separate script file also makes it easier to inspect diffs and working on them, given that the Xcode build phase script editor window is far from a good text interface for coding.

Testing

If the UI tests pass in CI, we're good.

Regression Notes

1. Potential unintended areas of impact – N.A.
2. What I did to test those areas of impact (or what existing automated tests I relied on) – N.A.
3. What automated tests I added (or what prevented me from doing so) – N.A.

---

PR submission checklist:

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

UI changes testing checklist: Not a UI PR.

[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	pr21192-8badab3
	Version	22.9
	Bundle ID	com.jetpack.alpha
	Commit	8badab3
	App Center Build	jetpack-installable-builds #5544

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 WordPress Alpha by scanning the QR code below to install the corresponding build.

	App Name	WordPress Alpha
	Configuration	Release-Alpha
	Build Number	pr21192-8badab3
	Version	22.9
	Bundle ID	org.wordpress.alpha
	Commit	8badab3
	App Center Build	WPiOS - One-Offs #6512

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

[jostnes]

Thanks for doing this @mokagio! It'll definitely be easier to monitor current configurations with this script, for example, I wasn't aware that this was the current setting

# Disable the hardware keyboard in the Simulator
defaults write com.apple.iphonesimulator ConnectHardwareKeyboard -bool false

CI is 🟢 looks good to

One question - will the same be done for the WCiOS project?