App Intents: extract localizable strings from code at code freeze

[crazytonyli]

Description

Relates to #25753.

The deleted Localizable.strings files were added in #25753. They were added because, on iOS 17, the App Intents strings looks up the strings tables in the extension bundle, not the app bundle. But from iOS 18, they can look up from the app bundle. This discrepancy is validated on simulators. I'm not sure if that's the case on real devices too. I don't have an iOS 17 device.

This PR simplified the localizable strings, by dropping the strings tables in the extension bundle (again, which is newly added in #25753). That means iOS 17 don't get the translated strings. I think this is an okay compromise, because we don't have many users on iOS 17 and we are going to drop it in two months.

To make sure the App Intents strings (used via LocalizedStringResource) are translated, the code freeze now extracts the LocalizedStringResource call sites with xcstringstool (genstrings cannot parse them) and merges them into the GlotPress upload.

[dangermattic]

	1 Warning
⚠️	Translation files *.lproj/Localizable.strings should only be updated on a release branch.

Generated by 🚫 Danger

[wpmobilebot]

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

	App Name	WordPress
	Configuration	Release-Alpha
	Build Number	33324
	Version	PR #25766
	Bundle ID	org.wordpress.alpha
	Commit	5778339
	Installation URL	66cp8br8u0jvg

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

[wpmobilebot]

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

	App Name	Jetpack
	Configuration	Release-Alpha
	Build Number	33324
	Version	PR #25766
	Bundle ID	com.jetpack.alpha
	Commit	5778339
	Installation URL	0ri26u720ht98

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

[mokagio]

According to Opus 4.8, there might be an issue in the implementation. See #25805

[wpmobilebot]

Version 27.1 has now entered code-freeze, so the milestone of this PR has been updated to 27.2.

[crazytonyli]

@mokagio Thanks for the review!

I decided to go with another direction. Keep the existing translations (there is only a couple), and reusing the WIP plural support translation pipeline (when its ready) for the new App Intents strings.

With this direction, the existing apps work as it is, as long as we don't delete the existing translations. But we won't be able to translate new App Intents strings, until the plural support translation pipeline is ready.

Again, this is for simplicity's sake.

[mokagio]

That means iOS 17 don't get the translated strings. I think this is an okay compromise, because we don't have many users on iOS 17 and we are going to drop it in two months.

Solid.