stream: fix merge() idle source draining

[trivikr]

This updates stream/iter merge() so fast sources are not pulled to
completion while the merged consumer is idle.

Previously, after a source produced a batch, merge() immediately scheduled
another next() for that same source. If the merged iterator yielded once and
then the consumer paused, fast sources could continue draining in the
background.

The multi-source merge path now waits until the consumer requests the next
merged item before pulling again from the source that produced the previous
item.

Fixes: #63566

---

Assisted-by: openai:gpt-5.5

[nodejs-github-bot]

Review requested:

• @nodejs/streams

[codecov]

Codecov Report

❌ Patch coverage is 89.28571% with 12 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.33%. Comparing base (37779fd) to head (d4d7730).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
lib/internal/streams/iter/consumers.js	89.28%	12 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #63567      +/-   ##
==========================================
- Coverage   90.34%   90.33%   -0.02%     
==========================================
  Files         732      732              
  Lines      236689   236754      +65     
  Branches    44586    44610      +24     
==========================================
+ Hits       213839   213870      +31     
- Misses      14550    14602      +52     
+ Partials     8300     8282      -18     

Files with missing lines	Coverage Δ
lib/internal/streams/iter/consumers.js	96.48% <89.28%> (-0.14%)	⬇️

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