fix(socks5-proxy-agent): use per-origin pools to prevent cross-origin routing

[deepview-autofix]

The Socks5ProxyAgent stored a single Pool keyed implicitly to the first origin it saw and reused it for every subsequent request. When a second request targeted a different origin, it was dispatched through the existing pool whose connect callback tunnelled to the original origin, causing the request to reach the wrong host (and potentially leaking headers/credentials intended for origin B to origin A).

Track pools in a Map keyed by origin so each origin gets its own pool and SOCKS5 tunnel.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 90.47619% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 93.04%. Comparing base (bc0a19c) to head (9457103).

Files with missing lines	Patch %	Lines
lib/dispatcher/socks5-proxy-agent.js	90.47%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5041   +/-   ##
=======================================
  Coverage   93.03%   93.04%           
=======================================
  Files         110      110           
  Lines       35793    35802    +9     
=======================================
+ Hits        33301    33312   +11     
+ Misses       2492     2490    -2     

☔ 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

[mcollina]

Are you sure the test was failing without the changes in lib? Why is that happening?

[ChALkeR]

@mcollina Yes, this test was failing prior to the fix and I rechecked it manually.
Origin (and thus host + port) was cached on the first request and reused on the second one.
Which is what this bug is about.

main:

test at test/socks5-proxy-agent.js:228:1
✖ Socks5ProxyAgent - requests to different origins are routed correctly (4.945292ms)
  AssertionError [ERR_ASSERTION]: request to origin B must reach server B, not server A

The result for the second request in test was { server: 'A', path: '/b' }
As it was routed to and answered by server A.