Fix: race condition on attachedGestures in updateHandlers (#3425)

## Description

Our production apps are regularly crashing with the following
stacktracke:
```
Non-fatal Exception: io.invertase.firebase.crashlytics.JavaScriptError: Cannot read property 'handlers' of undefined
       at .anonymous(address at node_modules/react-native-gesture-handler/src/handlers/gestures/GestureDetector/updateHandlers.ts:51:ghQueueMicrotask$argument_0)
       at .anonymous(address at node_modules/react-native/Libraries/Core/Timers/immediateShim.js:46:global.queueMicrotask$argument_0)
```
This seems to be caused by a race condition on the number of gestures in
`preparedGesture.attachedGestures`. This PR fixes that race condition by
storing the value of `preparedGesture.attachedGestures` from when the
micro task was scheduled.

## Test plan

Run example apps

Author: uyt95

src/handlers/gestures/GestureDetector/updateHandlers.ts

@@ -30,6 +30,9 @@ export function updateHandlers(
     }
   }
 
+  // Store attached gestures to avoid crash when gestures changed after queueing micro task
+  const attachedGestures = preparedGesture.attachedGestures;
+
   // Use queueMicrotask to extract handlerTags, because when it's ran, all refs should be updated
   // and handlerTags in BaseGesture references should be updated in the loop above (we need to wait
   // in case of external relations)
@@ -38,12 +41,17 @@ export function updateHandlers(
       return;
     }
 
+    // Stop if attached gestures changed after queueing micro task
+    if (attachedGestures !== preparedGesture.attachedGestures) {
+      return;
+    }
+
     // If amount of gesture configs changes, we need to update the callbacks in shared value
     let shouldUpdateSharedValueIfUsed =
-      preparedGesture.attachedGestures.length !== newGestures.length;
+      attachedGestures.length !== newGestures.length;
 
     for (let i = 0; i < newGestures.length; i++) {
-      const handler = preparedGesture.attachedGestures[i];
+      const handler = attachedGestures[i];
 
       // If the gestureId is different (gesture isn't wrapped with useMemo or its dependencies changed),
       // we need to update the shared value, assuming the gesture runs on UI thread or the thread changed
@@ -70,7 +78,7 @@ export function updateHandlers(
     }
 
     if (preparedGesture.animatedHandlers && shouldUpdateSharedValueIfUsed) {
-      const newHandlersValue = preparedGesture.attachedGestures
+      const newHandlersValue = attachedGestures
         .filter((g) => g.shouldUseReanimated) // Ignore gestures that shouldn't run on UI
         .map((g) => g.handlers) as unknown as HandlerCallbacks<
         Record<string, unknown>