test: upstream fix for release mode iOS crash

This fixes a null-handling crash bug upstream that we trigger in
functions and firestore

It is preseent in 0.77.1, and 0.78.0
It is fixed upstream in 0.77.2 and 0.78.1 and 0.79.0

This patch may be dropped once one of those versions with the fixed
is adopted here

The crash would not be triggered in our "other" platform support as
those don't rely on the native null handling in functions and firestore

Author: mikehardy

tests/patches/react-native+0.77.1.patch

@@ -0,0 +1,20 @@
+diff --git a/node_modules/react-native/ReactCommon/react/nativemodule/core/platform/ios/ReactCommon/RCTInteropTurboModule.mm b/node_modules/react-native/ReactCommon/react/nativemodule/core/platform/ios/ReactCommon/RCTInteropTurboModule.mm
+index 9ff5638..740a202 100644
+--- a/node_modules/react-native/ReactCommon/react/nativemodule/core/platform/ios/ReactCommon/RCTInteropTurboModule.mm
++++ b/node_modules/react-native/ReactCommon/react/nativemodule/core/platform/ios/ReactCommon/RCTInteropTurboModule.mm
+@@ -446,6 +446,15 @@ void ObjCInteropTurboModule::setInvocationArg(
+ 
+     if (objCArgType == @encode(id)) {
+       id arg = RCTConvertTo<id>(selector, objCArg);
++
++      // Handle the special case where there is an argument and it must be nil
++      // Without this check, the JS side will receive an object.
++      // See: discussion at
++      // https://github.com/facebook/react-native/pull/49250#issuecomment-2668465893
++      if (arg == [NSNull null]) {
++        return;
++      }
++
+       if (arg) {
+         [retainedObjectsForInvocation addObject:arg];
+       }