fix crash on non-critical path, e.g., setTimeout

[ehsemloh]

Summary:

Issue: #51664

Exceptions on non-critical path crash the app. This happened locations such as callback in setTimeout, onPress callback of <Pressable>, less defensive 3rd-parties libraries (on code level) can also crash the app on these paths.

Exception in ReactFabric::extractEvents crashes the app.

The above behaviors does not exist in older versions. In React web, exceptions on those paths are treated same way as async operations and are handled by global handler.

Changelog:

[IOS] [FIXED] - Fix crash on non-critical path

Test Plan:

1. Callback in setTimeout:

setTimeout(() => {
  throw new Error('SWW');
}, 10000);

2. Callback in Pressable:

<Pressable onPress={() => {
  throw new Error('SWW');
}}/>

3. Simulated exception in ReactFabric::extractEvents

let deathCount = 0; // use this variable to pass the bootstrap

var ResponderEventPlugin = {
    _getResponder: function () {
      return responderInst;
    },
    eventTypes: eventTypes,
    extractEvents: function (
      topLevelType,
      targetInst,
      nativeEvent,
      nativeEventTarget
    ) {   
...
      if (deathCount++ === 300) { // use `===` to simulate an one-off exception, e.g., `Unsupported top level event type ...` 
        throw new Error('SWW');
      }
...

[javache]

This is intended behaviour, and should match what you saw in the old architecture.

React on web doesn't handle this case specifically either, but the default for browsers is that unhandled errors don't stop the runtime or prevent further JS execution. We're looking into matching this behaviour in the native runtime too, but this will require a more considered rollout than this PR.