[updates] fix error recovery on android

[Kudo]

Why

add bridgeless support for expo-updates's error recovery on android
close ENG-11707

How

• the DefaultJSExceptionHandler from DevSupportManager doesn't work on bridgeless mode. we should add a ReactNativeHostHandler.onReactInstanceException to pull the exception from ReactHost
• add ReactApplication.restart() to support both bridgeless and bridge mode.
• decouple from ReactNativeHost

Test Plan

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).

[expo-bot]

The Pull Request introduced fingerprint changes against the base commit: 796d42a

Fingerprint diff

[
  {
    "type": "dir",
    "filePath": "../../packages/expo-modules-core/android",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "de8d3310de13d9a5605e3879286bb29fd04443eb"
  },
  {
    "type": "dir",
    "filePath": "../../packages/expo-updates/android",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "d1e2a67bbf7990d98ba4b62369007d725ac32645"
  },
  {
    "type": "dir",
    "filePath": "../../packages/expo/android",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "dde693a1c8cad65bef7da0050bcd720f99343ed1"
  }
]

---

Generated by PR labeler 🤖

[linear]

ENG-11707 [expo-updates] Bridgeless mode support

[Kudo]

the sdk check-packages failure would be fixed by #27891

[wschurman]

Main change is to add asserts for our assumptions about code we expect to only run in bridgeless and code we expect to never run in bridgeless.

[wschurman]

since overriding the exception handler doesn't work on bridgeless, should we update ErrorRecovery to not register the error when in bridgeless mode?

edit: I see that the registration is done in onDidCreateReactInstanceManager/onDidCreateReactInstance so it shouldn't be running on bridgeless. let's add an assert to registerErrorHandler to assert non-bridgeless and also add an assert to onReactInstanceException (here) to assert bridgeless, just so that if upstream (expo-modules-core) is changed our assumptions hold.

[Kudo]

tried to split that as two different implementation, hopes that looks good

  private fun registerErrorHandler(reactContext: ReactContext) {
    if (ReactFeatureFlags.enableBridgelessArchitecture) {
      registerErrorHandlerImplBridgeless(reactContext)
    } else {
      registerErrorHandlerImplBridge(reactContext)
    }
  }