fix(node/http): stop leaking TCP wrappers on HTTPS upgrade with createConnection TLSSocket

[magurotuna]

Fixes a Node-compat HTTP/TLS bug where https.request() could leak native TCP wrappers when createConnection returns a pre-created TLSSocket and the request upgrades the connection.

This is the same pattern used by npm:ws - create the TLS socket first with tls.connect(), then pass it to https.request({ createConnection }).

This patch:

• reuses the original encrypted TLSSocket during the upgrade path instead of creating a replacement socket
• skips the sock-init workaround for sockets that are already encrypted
• waits for secureConnect before flushing the request on pre-created TLSSockets
• preserves the TLS-upgrade state needed when the handle is reinitialized

User-visible improvement

With the attached repro, RSS no longer grows linearly with each upgraded connection.

Before this patch:

• RSS grows from 102 MB to 349 MB over about 4,053 connections in a comparable ~5 minute run

After this patch:

• RSS grows from 96 MB to 118 MB over about 3,920 connections in a comparable ~5 minute run
• heap usage stays roughly flat
• the process reaches a steady state instead of continuing to climb

Script used can be found at https://github.com/magurotuna/tls_then_upgrade/blob/main/client.ts