[RN][iOS] Add matrix for Debug/Release, New/Legacy Architecture, (No)Hermes

[cipolleschi]

Summary

This PR is the dual of the Matrix Tests we added to the Android Template a couple of weeks ago. It adds the same tests to iOS, to verify that the template builds with both architectures and with both configurations (Debug/Release).. And it tests that the template works with both Hermes and without it.

Changelog

[iOS] [Added] - Test iOS template with both architectures and configurations

Test Plan

CI is green in all the 8 new jobs.

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
ios	-	universal	n/a	--

Base commit: 3d82f7e
Branch: main

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	7,617,874	-16,553
android	hermes	armeabi-v7a	7,032,126	-14,434
android	hermes	x86	7,917,927	-18,430
android	hermes	x86_64	7,891,556	-16,857
android	jsc	arm64-v8a	9,495,283	-16,634
android	jsc	armeabi-v7a	8,272,914	-14,284
android	jsc	x86	9,433,074	-18,374
android	jsc	x86_64	10,026,064	-16,632

Base commit: 3d82f7e
Branch: main

[facebook-github-bot]

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[mikehardy]

would it be possible to add a flipper or not (since I think flipper in release mode had a problem recently, and release mode issues are typically not discovered until later in the RC cycle after the first few build checks)

And of course my favorite we add a use_frameworks check (with possibly both linkages - so it's actually a tri-state, no frameworks, frameworks+dynamic, frameworks+static)

These are the variations I'm currently aware of

I expect failure in hermes+frameworks+dynamic, and flipper+frameworks+any and newarch+frameworks+any, but on the good side, the other permutations are all working I think

[cipolleschi]

As discussed offline (but leaving the reply here for future doc), yes.

I plan to add the Flipper Yes/No, excluding all the WithFlipper+Release because flipper is not added by default in Release.

For use framework, yes... it is possible, but requires some more changes also in the podfiles...

I'll probably add them in a separate PR, though. Just not to add too many things at once.

[mikehardy]

Totally agree with incremental improvement in all things, and specifically here. But as a brainstorm for a future PR: I also just remembered macCatalyst builds. That was an odyssey getting them working again after they broke in 0.63, would be nice to have a canary here that would tell us if they broke again.

[facebook-github-bot]

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[react-native-bot]

This pull request was successfully merged by @cipolleschi in 4352459.

^{When will my fix make it into a release? | Upcoming Releases}