[core][updates] fix error recovery on android

[Kudo]

Why

the error recovery of updates was broken since https://github.com/expo/expo/pull/27629/files#diff-b034a3a37c87b036bb0d9c0549d6701774c79fedb4892dd44807d8947d75d4fbL27-R37. apparently when ReactContext is available, it's too late for error recovery because bundle is loaded and may throw exceptions already.

How

• i feel [core][updates] Add bridgeless support for ReactNativeHostHandler #27629's change is correct for onDidCreateReactInstance. for error recovery we sound like need to call point between onWillCreateReactInstance and DevSupportManager available (error recovery requires DevSupportManager to detect exceptions). this pr introduces a new onDidCreateDevSupportManager for this purpose.
• also fix incorrect onWillCreateReactInstance timing on bridgeless mode
• seen a detox failed from proguard that i have to add an additional proguard rule to fix that.

Test Plan

test based on #28050
i need further change to the detox e2e

• detox does not support reload well, it will encounter the detox error and enter infinite waiting loop. the reason is that the detox access to the old ReactContext which is not the same with the new ReactContext reloading from error recovery. i have to patch the [expo-update][e2e] Add error recovery e2e test #28050 test

  diff --git a/packages/expo-updates/e2e/fixtures/Updates-error-recovery.e2e.ts b/packages/expo-updates/e2e/fixtures/Updates-error-recovery.e2e.ts
  index 016a204516..92b429c506 100644
  --- a/packages/expo-updates/e2e/fixtures/Updates-error-recovery.e2e.ts
  +++ b/packages/expo-updates/e2e/fixtures/Updates-error-recovery.e2e.ts
  @@ -19,6 +19,23 @@ const waitForAppToBecomeVisible = async () => {
       .withTimeout(2000);
   };
  
  +function launchAppWithTimeout(timeout: number) {
  +  return new Promise(async (resolve, reject) => {
  +    setTimeout(() => {
  +      reject(new Error('Launch timed out'));
  +    }, timeout);
  +
  +    try {
  +      await device.launchApp({
  +        newInstance: true,
  +      });
  +      resolve(null);  // If successful, resolve the promise.
  +    } catch (error) {
  +      reject(error);  // If the launchApp itself fails, reject the promise.
  +    }
  +  });
  +}
  +
   describe('Error recovery tests', () => {
     afterEach(async () => {
       await device.uninstallApp();
  @@ -69,9 +86,7 @@ describe('Error recovery tests', () => {
       // we don't check current update ID header or failed update IDs header since the behavior for this request is not defined
       // (we don't guarantee current update to be set during a crash or the launch failure to have been registered yet)
       await jestExpect(
  -      device.launchApp({
  -        newInstance: true,
  -      })
  +      launchAppWithTimeout(2000)
       ).rejects.toThrow();
       const request2 = await Server.waitForUpdateRequest(10000);
       const request2EmbeddedUpdateId = request2.headers['expo-embedded-update-id'];

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: 8b52a69

Fingerprint diff

[
  {
    "type": "dir",
    "filePath": "../../packages/expo-modules-core/android",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "5c63d7d66259fecbedd3b302ede82ac88406c117"
  },
  {
    "type": "dir",
    "filePath": "../../packages/expo-updates/android",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "1ee15c237dad83e46e687aa95c575dcb8c3d7f24"
  },
  {
    "type": "dir",
    "filePath": "../../packages/expo/android",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "0bde56915036ba0e2595e085e24a1f4b3c6d9a80"
  }
]

---

Generated by PR labeler 🤖

[Kudo]

android instrumentation test was failed from #28163 (comment)