fix(ext/node): preserve TLS upgrade state on reconnect - #32838

All committers have signed the CLA.

I’ve already signed the CLA. It looks like the remaining checks are still waiting for workflow approval before they can report back.

Could a maintainer approve the workflow run when convenient?

Hey @bartlomieju ,I just pushed the fixes for the previous CI errors. The workflow needs re-approval due to the force-push. Mind approving it again when convenient? Thanks!

Hey @bartlomieju, I pushed a follow-up fix for the Windows HTTP/2 callback type mismatch that was failing CI.

This update switches the affected nghttp2 callback/data provider usage to the *2 APIs (set_select_padding_callback2, nghttp2_data_provider2, submit_request2, submit_response2, and submit_data2) so the callback signatures line up with the generated binding types on Windows.

Locally I re-ran:

• cargo build --locked --bin deno --bin denort --bin test_server --features=panic-trace
• deno run --allow-write --allow-read --allow-run --allow-net --allow-env ./tools/lint.js

Could someone re-approve/re-run CI on the latest commit when convenient? Thanks!

LGTM, thanks!

Thanks for the review and for merging this!