fix(h2): handle GOAWAY for CONNECT streams

[mcollina]

This relates to...

Backport of the fix for #5638 to v7.x.

Rationale

The v7.x HTTP/2 implementation predates the stream-severing machinery on main, but plain CONNECT streams have the analogous failure: unlike ordinary and WebSocket streams, they do not attach an error handler. GOAWAY teardown can therefore emit an unhandled stream error and terminate the process.

Changes

Features

N/A

Bug Fixes

• Route CONNECT stream errors through the request's existing abort path.
• Add a raw h2c regression test covering CONNECT followed by GOAWAY(lastStreamID=0).

Breaking Changes and Deprecations

N/A

Status

• I have read and agreed to the Developer's Certificate of Origin
• Tested
• Benchmarked (optional)
• Documented (not applicable)
• Review ready
• In review
• Merge ready

Validation

• npx borp -p "test/issue-5638.js"
• npx borp -p "test/http2-goaway.js" -p "test/http2-dispatcher.js"
• npx eslint lib/dispatcher/client-h2.js test/issue-5638.js
• git diff origin/v7.x...HEAD --check

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.15%. Comparing base (c26f943) to head (0fbbdfc).

Additional details and impacted files

@@           Coverage Diff           @@
##             v7.x    #5640   +/-   ##
=======================================
  Coverage   93.15%   93.15%           
=======================================
  Files         112      112           
  Lines       36810    36811    +1     
=======================================
+ Hits        34291    34293    +2     
+ Misses       2519     2518    -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 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.