stream: preserve mutable chunks in Web Stream adapters

[seungwoo505]

When a Node.js writable is converted with Writable.toWeb(), the Web Streams
write() promise can currently settle as soon as the native write() call
returns true. That return value only represents backpressure, so the native
stream may still retain the supplied mutable BufferSource. Reusing the buffer
after awaiting the Web write can therefore change bytes that have not yet been
consumed.

This change:

• waits for the native per-write callback when the stream is an uncorked,
  unmodified Writable;
• coordinates callback completion with drain, aborts, and native stream
  errors;
• passes a private same-brand BufferSource copy for Duplex, corked, overridden,
  and legacy write paths where waiting for a callback would change existing
  completion behavior;
• preserves HTTP input validation before fallback copies; and
• preserves SharedArrayBuffer backing for cloned views.

The original native Writable.prototype.write and
OutgoingMessage.prototype.write methods are captured so patched methods and
accessors are classified and invoked consistently.

Validation included:

• make -j4
• the changed Web Streams adapter, Duplex, and compression tests
• the existing Writable, Duplex, and Web Streams adapter test set
• CompressionStream WPT tests
• repeated async regression tests
• ESLint and git diff --check

Fixes: #64549

[nodejs-github-bot]

Review requested:

• @nodejs/http
• @nodejs/net
• @nodejs/streams