fix: duplicate symbols for ReactBrownfield

[hurali97]

Summary

Fixes - callstackincubator/rock#636

Problem
Consumer apps link BrownfieldLib (which, via CocoaPods / inherit! :complete, already includes ReactBrownfield in the same framework binary) and ship ReactBrownfield.xcframework for import ReactBrownfield and Xcode integration. That loads two copies of the same Swift/ObjC types into the process, which surfaces as duplicate Objective‑C class registration and related duplicate-symbol issues.

Solution
After packageIosAction completes, if ReactBrownfield.xcframework exists under the package output directory, we run the same stripFrameworkBinary step already used for Brownie.xcframework and BrownfieldNavigation.xcframework. The xcframework stays usable for imports and Swift interfaces, while its Mach-O is replaced with a stub so implementations are not duplicated in apps that embed both BrownfieldLib and ReactBrownfield.xcframework.

Test plan

Before

Before.mov

After

After.mov

[Copilot]

Pull request overview

This PR updates the iOS packaging command to prevent duplicate symbol / duplicate Objective‑C class registration issues when consumer apps embed both BrownfieldLib (which already contains ReactBrownfield symbols) and ReactBrownfield.xcframework.

Changes:

• Add detection of ReactBrownfield.xcframework in the package output directory.
• Run stripFrameworkBinary on ReactBrownfield.xcframework to make it interface-only when present.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.