https: handle invalid TLS options in proxied requests

[christianaurichzm]

Invalid TLS options can cause an uncaught exception when an HTTPS request uses a proxy.

After the proxy responds to CONNECT, tls.connect() is called from the socket read handler. If TLS option validation throws at that point, the exception is outside the original https.request() call.

Catch the error, close the tunnel socket, and propagate it to the request's 'error' handler.

The new test covers invalid minVersion, ciphers, and secureProtocol options.

[nodejs-github-bot]

Review requested:

• @nodejs/crypto
• @nodejs/http
• @nodejs/net

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.27%. Comparing base (67e66b8) to head (663dfa8).
⚠️ Report is 32 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main   #66096    +/-   ##
========================================
  Coverage   90.27%   90.27%            
========================================
  Files         789      790     +1     
  Lines      271473   271600   +127     
  Branches    51808    51837    +29     
========================================
+ Hits       245066   245187   +121     
- Misses      16880    16922    +42     
+ Partials     9527     9491    -36     

Files with missing lines	Coverage Δ
lib/https.js	97.21% <100.00%> (+0.03%)	⬆️

... and 69 files with indirect coverage changes

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

[nodejs-github-bot]

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