Review requested:

• @nodejs/quic

@pimtery @jasnell Not to be merged now. It is to be prepared when newer nghttp3 arrives in node.js
Also cherry picking on the update PR is possible.

Expect building to fail until the update.

The newer nghttp3 had been merged. Separate from this also ngtcp3 needs an update to address the changes.
It is on my TODO list, but I am chasing again another race condition in sendpendingdata....., so will take a while.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.30%. Comparing base (e2d7b34) to head (6875095).
⚠️ Report is 267 commits behind head on main.

@@            Coverage Diff             @@
##             main   #64574      +/-   ##
==========================================
- Coverage   90.31%   90.30%   -0.01%     
==========================================
  Files         759      759              
  Lines      248290   248342      +52     
  Branches    46859    46876      +17     
==========================================
+ Hits       224241   224273      +32     
- Misses      15472    15505      +33     
+ Partials     8577     8564      -13     

see 49 files with indirect coverage changes

• ❄️ 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.

I have also added the ngtcp2 change.
It seems we should think perspectively about changing the QuicError interface, since we can have two independent error codes simultaneously on the tx and rx sides. This may be useful for low-level implementation. Though not pressing for this PR.

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

Landed in eae0ca3