stream: skip null output from stateful transforms

[trivikr]

Fixes: #64461

Stateful transforms currently pass null output to the flattening
helpers, causing ERR_INVALID_ARG_TYPE. Transform output
normalization defines null as no output.

Skip null before flattening stateful transform output in both the
sync and async paths.

[nodejs-github-bot]

Review requested:

• @nodejs/streams

[nodejs-github-bot]

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.24%. Comparing base (14166a5) to head (3c2ae5a).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #64462      +/-   ##
==========================================
+ Coverage   90.23%   90.24%   +0.01%     
==========================================
  Files         741      741              
  Lines      241375   241606     +231     
  Branches    45483    45536      +53     
==========================================
+ Hits       217800   218036     +236     
+ Misses      15129    15109      -20     
- Partials     8446     8461      +15     

Files with missing lines	Coverage Δ
lib/internal/streams/iter/pull.js	83.89% <100.00%> (+0.03%)	⬆️

... and 35 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]

I was under the impression that stateful transformers should not be yielding null at all, they should just mark the iterator as done to mark end-of-output?

[trivikr]

stateful transformers should not be yielding null at all

A null output is accepted as per specification §9.3 Transforms

Transform return values are flexible. A transform may return: null (no output), Uint8Array[] (a batch), a single Uint8Array, a USVString (UTF-8 encoded), an iterable or async iterable (flattened), or a promise (awaited, async only).

And the bug is explained in #64461

@Renegade334 Would you like to create an issue on the specification?

I don't see a block from you, but I've removed author-ready.
I'll re-add it and land the fix based on your response.