Fix iOS deployment targets for CocoaPods resource bundles

[Marve10s]

Summary:

CocoaPods resource bundles can retain deployment targets such as iOS 9.0 even after React Native raises their library target to iOS 15.1. Xcode 27 rejects those bundle targets, blocking the build described in #58555.

updateOSDeploymentTarget only visits each pod's native target. Include its resource bundle targets in the same traversal so every bundle receives React Native's minimum deployment target while preserving higher existing values.

Fixes #58555.

Changelog:

[IOS] [FIXED] - Apply React Native's minimum iOS deployment target to CocoaPods resource bundles.

Test Plan:

• ruby packages/react-native/scripts/cocoapods/__tests__/utils-test.rb --name test_updateOSDeploymentTarget_updatesNativeAndResourceBundleTargets: passes with 1 test and 3 assertions. Before the fix, it fails because bundle targets remain at 9.0 and 12.4. Covers multiple bundles, Debug and Release configurations, missing deployment targets, and preservation of higher values.
• ruby packages/react-native/scripts/cocoapods/__tests__/utils-test.rb: 67 tests, 170 assertions, 2 failures. Untouched main at ba1ede621cf5fc63b81fc3e2645f3014c0fe0c03 has the same failures in test_SetGCCPreprocessorDefinitionForHermes_itSetsThePreprocessorForDebug and test_updateSearchPaths_whenUseFrameworks_addsSearchPaths.
• A headless check using real Xcodeproj targets reproduces the skipped bundles with the published React Native 0.87.1 helper. With this fix, all expected deployment settings persist after saving and reopening the project. This exercises the helper directly, without running pod install or a full Xcode build.
• git diff --check: passes.

A full Xcode 27 build was not run.

[meta-cla]

Hi @Marve10s!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!