stream: fix Writable.toWeb() desiredSize for non-object-mode

[mcollina]

Writable.toWeb() used a plain { highWaterMark } as the queuing strategy for non-object-mode streams, which meant no size function was provided. The WritableStream defaulted to counting each chunk as size 1, so desiredSize was incorrect (e.g. a 3-byte Uint8Array was counted as size 1 instead of 3).

Add a size() function to the strategy that mirrors how the Node.js stream computes chunk length: byteLength for typed arrays, length for strings/buffers, falling back to 1.

Fixes: #56269

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.66%. Comparing base (c3dd52a) to head (33b3fe0).
⚠️ Report is 103 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #62986      +/-   ##
==========================================
+ Coverage   89.61%   89.66%   +0.04%     
==========================================
  Files         706      707       +1     
  Lines      219136   219506     +370     
  Branches    41981    42077      +96     
==========================================
+ Hits       196376   196815     +439     
+ Misses      14671    14604      -67     
+ Partials     8089     8087       -2     

Files with missing lines	Coverage Δ
lib/internal/webstreams/adapters.js	86.66% <100.00%> (+0.05%)	⬆️

... and 74 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.

[Renegade334]

Add a size() function to the strategy that mirrors how the Node.js stream computes chunk length: byteLength for typed arrays, length for strings/buffers, falling back to 1.

Technically, I think the Node.js side deals exclusively in .length, not that it should make a difference to the outcome.