test_runner: avoid waiting on inherited stdio with force exit

[dayun6530]

Fixes: #66336

When --test-force-exit is used, the parent test runner waits for both
the test file process to exit and its stdout stream to finish.

If the test file leaks a child process with inherited stdio, that child
keeps the stdout pipe open even after the test file process exits. This
causes the test runner to remain alive until the leaked child exits.

Use the test:summary event as an additional completion signal when
--test-force-exit is enabled. Once the summary has been received, the
test report has completed and the parent no longer needs to wait for EOF
from stdout.

The existing stdout completion path is kept as a fallback.

A regression test is included for a leaked child process with inherited
stdio.

[nodejs-github-bot]

Review requested:

• @nodejs/test_runner

[addaleax]

If the test file leaks a child process with inherited stdio, that child
keeps the stdout pipe open even after the test file process exits. This
causes the test runner to remain alive until the leaked child exits.

That can happen regardless of the forced exit flag, right?

[codecov]

Codecov Report

❌ Patch coverage is 86.95652% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.43%. Comparing base (4486dce) to head (7d48358).
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
lib/internal/test_runner/runner.js	86.95%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #66390      +/-   ##
==========================================
+ Coverage   90.42%   90.43%   +0.01%     
==========================================
  Files         791      791              
  Lines      275611   275591      -20     
  Branches    52845    52843       -2     
==========================================
+ Hits       249209   249229      +20     
+ Misses      16810    16763      -47     
- Partials     9592     9599       +7     

Files with missing lines	Coverage Δ
lib/internal/test_runner/runner.js	94.97% <86.95%> (-0.16%)	⬇️

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

[dayun6530]

Yes, the inherited stdout pipe can remain open regardless of --test-force-exit. The distinction here is that with --test-force-exit, once all known tests have completed, the runner should not remain blocked waiting for that inherited pipe to reach EOF. This change only bypasses that wait in the forceExit case; without it, the existing stdout completion behavior is preserved.