fix(socks5): use configured connector in Socks5ProxyAgent

[trivikr]

This relates to...

Fixes: #5167

Rationale

Socks5ProxyAgent initializes a connector from options.connect or buildConnector({ ...options.proxyTls }), but createSocks5Connection() connected to the SOCKS5 proxy with net.connect() directly.
This bypassed custom proxy connectors and could prevent proxyTls options from being honored.

Changes

• Use the configured connector when opening the connection to the SOCKS5 proxy.
• Preserve SOCKS5 proxy TLS behavior by selecting the connector protocol based on proxyTls.

Features

N/A

Bug Fixes

Use configured connector in Socks5ProxyAgent

Breaking Changes and Deprecations

N/A

Status

• I have read and agreed to the Developer's Certificate of Origin
• Tested
• Benchmarked (optional)
• Documented
• Review ready
• In review
• Merge ready

Assisted-by: openai:gpt-5.5

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.26%. Comparing base (a07d945) to head (4904cbc).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5168      +/-   ##
==========================================
- Coverage   93.28%   93.26%   -0.02%     
==========================================
  Files         110      110              
  Lines       36313    36309       -4     
==========================================
- Hits        33873    33865       -8     
- Misses       2440     2444       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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

[mcollina]

lgtm