Support Promise<ArrayBuffer> in Java and ObjC TurboModules

[paradowstack]

Summary:

Promise<ArrayBuffer> was left out of the initial ArrayBuffer TurboModule landing because Android's promise-resolve path serializes through folly::dynamic, which cannot carry raw bytes. Codegen rejected the type on both iOS and Android so a spec that built on one platform could not silently diverge on the other.

This removes that guard and wires up Promise<ArrayBuffer> / Promise<?ArrayBuffer> on both platforms. On Android, codegen sets a per-method promiseResolveSupportsArrayBuffer flag on the JNI host function; when true, the resolve callback is a dedicated JCxxArrayBufferCallbackImpl / CxxArrayBufferCallbackImpl that hands a ByteBuffer (or null) straight to JSI as an ArrayBuffer without going through folly::dynamic. On iOS the resolve path already converted NSMutableData to a zero-copy jsi::ArrayBuffer - only the codegen rejection needed to come out.

Rebase note: This PR is based on main and still uses the landed buffer types (NSMutableData on iOS, ByteBuffer on Android). After the zero-copy follow-ups land (#57879, #57897), this branch should rebase and switch the use those types (RCTArrayBuffer * instead of NSMutableData *, ArrayBuffer instead of ByteBuffer).

Changelog:

[GENERAL] [ADDED] - Add Promise<ArrayBuffer> support for iOS (ObjC) and Android (Java/Kotlin) TurboModules

Test Plan:

• Codegen Java spec, JNI C++, ObjC header, and .mm snapshot tests updated for promiseArrayBuffer / promiseNullableArrayBuffer.
• RCTTurboModuleArrayBufferTests — testPromiseResolvesArrayBuffer covers the iOS resolve path end to end.
• RCTSampleTurboModule / SampleTurboModule add getAsyncBuffer, which resolves a Promise with a native-allocated buffer; SampleTurboModuleExample exercises it from JS.
• C++ API snapshots regenerated.