Cherry pick "Fix post_install_workaround downgrading development targets" to 0.66-stable

[Yonom]

Summary

ℹ️ This is a cherry-pick of #32633 to 0.66-stable

The __apply_Xcode_12_5_M1_post_install_workaround script changes the IPHONEOS_DEPLOYMENT_TARGET to 11.0 for all pods. This causes problems if the pods were targetting 12.0 or higher. Many expo modules are targetting 12.0.

I fixed this issue by checking the existing version and only bumping the target if it is lower than 11.0.

See also: this discussion post by @mikehardy reactwg/react-native-releases#1 (comment)

Changelog

[iOS] [Fixed] - __apply_Xcode_12_5_M1_post_install_workaround causing pods targetting iOS 12 and above to fail

Test Plan

Test (failing before this patch, passing after this patch)

1. pick an iOS Pod that has a minimum deployment target of iOS 12 or higher, I chose the Braintree package
2. npx react-native init myrnapp
3. Open ios/Podfile and add the pod as a dependency: pod 'Braintree', '~> 5' (and upgrade the Podfile target to 12 (platform :ios, '12.0'))
4. Compile the app.

Before applying this patch: ❌ Build fails because Braintree uses iOS 12 features and was downgraded to target 11.0
After applying this patch: ✅ Build succeeds

[pull-bot]

	Warnings
⚠️	❔ Base Branch - The base branch for this PR is something other than main. Are you sure you want to merge these changes into a stable release? If you are interested in backporting updates to an older release, the suggested approach is to land those changes on main first and then cherry-pick the commits into the branch for that release. The Releases Guide has more information.

Generated by 🚫 dangerJS against 65f7e8f

[analysis-bot]

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

Base commit: bba5e6b

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,943,010	+651,081
android	hermes	armeabi-v7a	8,477,902	+855,280
android	hermes	x86	9,362,026	+599,785
android	hermes	x86_64	9,329,256	+627,881
android	jsc	arm64-v8a	10,626,440	+946,232
android	jsc	armeabi-v7a	9,548,852	+881,265
android	jsc	x86	10,639,736	+1,003,716
android	jsc	x86_64	11,250,658	+1,017,901

Base commit: bba5e6b

[mikehardy]

Not sure of the process but I think the release management folks just command line these @lunaleaps ?
Not to take away from the fix itself being helpful 🙂

[lunaleaps]

@mikehardy I'm looking to change the process so the work is placed on the pick requester -- really the "work" here is figuring out merge conflicts and also triggering our CircleCI tests. Granted, our CircleCI tests don't really provide much coverage yet but I think building the habit won't hurt.