net,tls: fix session reuse with provided sockets

[harjothkhara]

Fixes: #64402

TLS sessions are bound to the authenticated server identity. When
tls.connect() wrapped a net.Socket connected to a literal IP address,
the socket did not retain its requested host and the TLS layer could fall
back to localhost. The offered session was then rejected because its
stored identity did not match. This surfaced after the host-binding
hardening in 9cc4e32375 (CVE-2026-48934).

Preserve the requested host for literal-IP socket connections before the
connection begins.
Add TLS 1.2 and TLS 1.3 regression coverage for both already-connected and
still-connecting provided sockets. Also verify that a session captured for
one literal-IP peer is rejected for another peer, hostname-based reuse stays
intact, and explicit servername continues to take precedence. The host is
recorded before both the literal-IP and DNS/autoSelectFamily branches.

Note: the same identity chain also feeds checkServerIdentity, so
certificate verification for wrapped literal-IP sockets now checks the
actual IP address instead of the historical localhost fallback,
matching what a direct tls.connect({ host }) connection already does.

Tests:

• python3 tools/test.py --mode=release parallel/test-tls-session-reuse-provided-socket parallel/test-tls-session-reuse-different-servername parallel/test-tls-secure-session parallel/test-https-agent-session-reuse parallel/test-net-connect-options-fd
• make lint

[nodejs-github-bot]

Review requested:

• @nodejs/net

[harjothkhara]

Could someone from @nodejs/net start CI and take a look? This fixes #64402.

[harjothkhara]

@lpinca @pimterry @jasnell follow-up: this fixes #64402, includes a regression test, and has had no review or CI run since July 11. Could someone take a look and start CI?

[MikeMcC399]

You requested a review in Slack and I notice that the PR branch is out of date, and there is no record of a full GitHub Actions CI run occurring.

Hopefully one of the network team will be able to respond to your request for review.

In the meantime, I would suggest that you rebase the branch in this PR according to the Pull requests documentation. That should cause an automatic CI run in GitHub Actions.

[harjothkhara]

Thanks @MikeMcC399, rebased on main. GitHub Actions CI is running now.