[Phase 4] Build React Native iOS E2E IPA artifact

[kieran-osgood-shopify]

Stack Context

This is Phase 4 of the BrowserStack Maestro E2E stack for Checkout Kit, stacked on the RN Android artifact workflow.

Parent issue: https://github.com/shop/issues-checkout-kit/issues/1098
Epic: https://github.com/shop/issues-checkout-kit/issues/1084

What?

Replaces the React Native iOS placeholder artifact workflow with a signed device archive/export path:

• installs JS dependencies with pnpm
• prepares sanitized sample app configuration via scripts/setup_storefront_env
• installs CocoaPods dependencies
• installs Bitrise certificates/profiles
• archives the RN iOS sample with xcodebuild archive for iphoneos
• exports an .ipa via xcodebuild -exportArchive
• exports E2E_REACT_NATIVE_IOS_APP_PATH
• documents iOS signing/export setup
• adds tests asserting the iOS workflow does not use local native SDK overrides

Why?

BrowserStack App Automate requires an .ipa for iOS real-device Maestro execution. RN E2E should validate the released native CocoaPods artifacts used by the React Native sample/module configuration, not local in-repo Swift SDK sources.

Validation

shadowenv exec -- ruby e2e/test/bitrise_pipeline_test.rb
shadowenv exec -- ruby e2e/test/e2e_matrix_test.rb
shadowenv exec -- ruby e2e/scripts/e2e_matrix validate
shadowenv exec -- bitrise validate -c e2e/bitrise.yml
shadowenv exec -- ruby -e 'require "yaml"; YAML.safe_load_file("e2e/bitrise.yml"); puts "e2e bitrise yaml parsed"'

[kieran-osgood-shopify]

• [Phase 7] Soft-launch E2E PR checks #364 : 2 dependent PRs (#401 , #417 )
• [Phase 6] Report E2E results to GitHub #363
• [Phase 5] Run BrowserStack Maestro from E2E matrix rows #362
• [Phase 4] Build React Native iOS E2E IPA artifact #361 👈 (View in Graphite)
• [Phase 3] Build React Native Android E2E APK artifact #360
• [Phase 2] Add Bitrise E2E pipeline skeleton #357
• [Phase1] Add E2E matrix launch smoke foundation #356
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[kiftio]

should we make these different?

We could keep timeout high, but drop no_output to 1800 or something to detect a hang?

[kiftio]

Is there a {{ .RubyVersion }} or worth extracting a variable...

Actually is it needed at all? The Gemfile.lock includes Ruby version, so a change would invalidate the cache when the ruby version changes without it