webstreams: allow shared array buffer sources in writable adapter

[Renegade334]

The webidl buffer source definition includes array buffers as well as array buffer views. Since node streams don't handle the former, #61913 added a transform step to the Writable.toWeb adapter to accept ArrayBuffers.

This PR expands the adapter behaviour to include SharedArrayBuffers – since the adapter already accepts views on shared array buffers, it doesn't make much sense to exclude these asymmetrically from the adapter logic.

[Renegade334]

This operation can throw (if chunk is a detached array buffer), so should be within the try/catch block.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.78%. Comparing base (ae1c0e4) to head (bb853fc).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #62163      +/-   ##
==========================================
- Coverage   89.79%   89.78%   -0.02%     
==========================================
  Files         697      697              
  Lines      215773   215773              
  Branches    41297    41305       +8     
==========================================
- Hits       193749   193724      -25     
- Misses      14117    14157      +40     
+ Partials     7907     7892      -15     

Files with missing lines	Coverage Δ
lib/internal/webstreams/adapters.js	86.44% <100.00%> (ø)
lib/internal/webstreams/compression.js	100.00% <100.00%> (ø)

... and 30 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[panva]

@Renegade334 how is this aligned with the spec and #62632?

[Renegade334]

This doesn't affect CompressionStream, just the Writable.toWeb adapter.

We currently have the scenario where the adapter will silently transform ArrayBuffer to Uint8Array before passing to the node stream (since ArrayBuffer is a valid buffer source in the web spec), but SharedArrayBuffers are not transformed and instead rejected – whereas node streams obviously accept views on SharedArrayBuffers, so there's unnecessary asymmetry.

CompressionStream correctly rejects both SABs and views on SABs, and this doesn't change.

[panva]

Ok, can you rebase your PR and -s the commit?

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/72558/