Restore dual architecture support for 3.9

[kieran-osgood-shopify]

TLDR;

The plan was to move up to new arch in #456 and release this under v4

This PR somewhat undoes this, and will release new arch with interop support under v3.9

V4 will be new arch only

This PR essentially undoes a number of improvements made in https://github.com/Shopify/checkout-sheet-kit-react-native/pull/456 around moving from async to sync api's (see getConfig / isAcceleratedCheckoutAvailable / isApplePayAvailable)

As those revert, this is no longer a breaking change and can be released under 3.9.0

I've validated there are no breaking changes to the JS contract by adding the "@microsoft/api-extractor": "^7.58.7", package and dumping the api contract from v3.8.4

What changes are you making?

• Restores @shopify/checkout-sheet-kit to 3.9.0 while preserving the v3 public async API.
• Keeps the JavaScript API compatible with both TurboModule and legacy NativeModules resolution.
• Restores old/new architecture support on Android and iOS by gating codegen/new-architecture dependencies and exporting legacy bridge Promise methods.
• Uses the finalized native SDKs: Android 3.6.3 and iOS 3.8.2 which have been released under the release-v3 release branch for 3.8.x
• Publishes React Native source and built declaration entry points so RN 0.81 transforms generated component specs correctly. Also prevents typecheck errors for consumers

How does Interop work

JS Layer

Before new arch we would access native modules via NativeModules.ShopifyCheckoutSheetKit, new arch is accessed via turbo modules TurboModuleRegistry.get(...)
We attempt turbo first, and fallback to native modules if it doesn't exist

Native Side

We have a few areas that are conditional to apply
On the iOS side we have to do conditional imports of turbo related headers and packaged via the #if RCT_NEW_ARCH_ENABLED directive and using the help-er install_modules_dependencies in the podspec

Gradle is a bit simpler because we just set a value in the env and pass it to a constructor for the react module

The rest of the native changes are reimplementing interfaces that the NativeModule system expects (e.g. getConstants / getName, and some of our bridge methods that are not codegenerated)

How to test

Builds have been distributed on Testflight and Play Store to tophat the build on New Arch.
I've done validation locally with new arch on and off and haven't run into any issues as of yet.

---

PR Checklist

Important

• I've added tests to support my implementation
• I have read and agree with the Contribution Guidelines.
• I have read and agree with the Code of Conduct.
• I've updated the README.

Releasing a new version of the kit?

• I have bumped the version number in the package.json file.

---

Tip

See the Contributing documentation for instructions on how to publish a new version of the library.

[kieran-osgood-shopify]

• Restore dual architecture support for 3.9 #487 👈 (View in Graphite)
• main

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

[github-actions]

Coverage Report

Lines	Statements	Branches	Functions
	99.12% (227/229)	94.61% (123/130)	100% (67/67)

[kieran-osgood-shopify]

FYI These all exist as turbo module plumbing - the typescript spec includes them modules/@shopify/checkout-sheet-kit/src/specs/NativeShopifyCheckoutSheetKit.ts but they're not actually run at runtime because we noop as we guard accelerated checkouts in JS via Platform.OS === 'ios'

[markmur]

@kieran-osgood-shopify want to make this change too while you're changing this file?

Related:

• Replace deprecated React Native activity access checkout-kit#655

[kieran-osgood-shopify]

This makes sense as we decided not to publish v4 and ive fixed the breaking changes