Deduplicate the ArrayBuffer helpers and align the ObjC, C++ and JNI implementations (#58004)

[christophpurrer]

Summary:

Follow-up cleanup on the ArrayBuffer TurboModule plumbing. No behaviour change except
the leak fix below.

• Move detail::throwIfDetached out of the header into a new
  react/bridging/ArrayBuffer.cpp, and drop the AsyncArrayBuffer::throwIfDetached
  wrapper that only forwarded to it. The JNI path now calls detail::throwIfDetached
  directly instead of going through AsyncArrayBuffer.
• Add detail::copyToOwnedBuffer, so the C++ bridging path and the tests build an
  owning buffer the same way instead of each hand-rolling a std::vector copy. The
  header no longer needs <span>/<string>.
• Rename the JArrayBuffer factories to say what they do about ownership:
  createOwning/createOwned/createUnowned become
  createWithOwnedBytes/createWithCopiedBytes/createWithUnownedBytes, matching the
  RCTArrayBuffer naming. Move invalidate() next to the other private members.
• RCTArrayBuffer uses synthesize rather than three hand-written accessors, and
  normalizes mutableBytes to NULL for a zero-length buffer so the documented
  "NULL exactly when empty" invariant holds for every factory.
• Run the caller's cleanup block before the designated initializer raises on a
  NULL/non-zero-length mismatch. Nothing else would ever release those bytes, so
  raising first leaked them.
• Treat only std::logic_error from tryGetMutableBuffer as "this runtime has no
  native buffer" on the JNI path, and log it once, instead of swallowing every
  std::exception.
• Keep the macOS mirror of RCTArrayBuffer byte-identical to the iOS one.

Changelog:
[General][Changed] - Rename the internal JArrayBuffer factories and deduplicate the ArrayBuffer helpers

Differential Revision: D116358593

[meta-codesync]

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