Change ArrayBuffer implementation from copyBuffer to moveBuffer (#56691)

[christophpurrer]

Summary:

Switches the jsi::ArrayBuffer ⇄ native byte buffer bridge in TurboModules from a copy-based implementation (OwnedMutableBuffer) to a zero-copy borrow implementation (BorrowedMutableBuffer) on the paths where the caller can guarantee the source memory's lifetime, eliminating an O(N) copy on every ArrayBuffer that crosses the JS/native boundary.

ReactCommon/react/bridging/ArrayBuffer.h — adds BorrowedMutableBuffer: holds a raw uint8_t* + size, plus an optional std::function<void()> release callback invoked from the destructor. Caller is responsible for keeping the underlying memory alive — typically by capturing a JNI global_ref or ARC-retained ObjC object in the release lambda. Non-copyable; documents thread-safety requirements (release may fire on the JS GC thread). OwnedMutableBuffer and the Bridging<std::vector<uint8_t>> specialization are preserved for paths where the source lifetime cannot be guaranteed.

Android — JavaTurboModule.cpp — wraps the Java ByteBuffer's direct memory in a BorrowedMutableBuffer. Pins the buffer with jni::make_global(jByteBuffer) and captures the global ref in the release lambda so Java GC cannot collect it while the JS ArrayBuffer is alive. Tightens the Ljava/nio/ByteBuffer; argument check from isObject() to isObject() && isArrayBuffer().

iOS — RCTTurboModule.mm — convertJSIObjectToObjCObject (sync arg path) returns NSMutableData dataWithBytesNoCopy:length:freeWhenDone:NO instead of copying via [NSData dataWithBytes:length:]. Safe because the JS ArrayBuffer outlives the synchronous call. convertReturnIdToJSIValue ArrayBufferKind (sync return path) wraps NSMutableData.mutableBytes with BorrowedMutableBuffer, retaining the NSMutableData via the block capture for the lifetime of the JS ArrayBuffer. convertObjCObjectToJSIValue (async/promise path) adds an NSData → ArrayBuffer branch that still copies via OwnedMutableBuffer, since the source NSData lifetime cannot be guaranteed past the async callback.

Codegen — serializeMethod.js + snapshot — ObjC++ spec generator now emits NSMutableData * (instead of NSData *) for ArrayBufferTypeAnnotation, both for parameters and return types. Module authors must update their ObjC implementations.

Changelog:
[General][Changed] - TurboModule ArrayBuffer transfers between JS and native are now zero-copy where caller lifetime can be guaranteed; ObjC TurboModule specs now use NSMutableData * for ArrayBufferTypeAnnotation parameters and return types

Differential Revision: D96034456

[meta-codesync]

@christophpurrer has exported this pull request. If you are a Meta employee, you can view the originating Diff in D96034456.