perf(jarm): coalesce concurrent fingerprints

[knakul853]

Summary

• share overlapping JARM calculations for the same proxy and destination
• forget results immediately after the active calculation, avoiding completed-result caching
• preserve every caller and matcher evaluation while removing duplicate sockets
• honor Aurora and Nuclei's explicit SOCKS5_PROXY scan route before legacy proxy environment variables

Evidence

• 16 real JARM templates: 128 -> 23 TCP connections (-82.0%)
• hidden JARM connections: 112 -> 7 (-93.75%)
• full 279-template controlled run: 60.40s -> 57.20s (-5.3%) after the separate deadline fix
• go test ./...
• go test -race ./... -run TestCoalesceJARM -count=10
• go test -race ./... -run 'Test(CoalesceJARM|JARMProxy)' -count=10

Routing correctness

Aurora exports its scan proxy as SOCKS5_PROXY. The JARM DSL helper previously ignored that variable and could bypass the intended route or fail on an unrelated HTTP proxy variable. The helper now prioritizes uppercase/lowercase SOCKS5 variables while retaining the legacy fallbacks.

Open in Codex: codex://threads/01a07d91-20ab-7a33-81ae-cfd2520595f4
Resume from CLI: codex resume 01a07d91-20ab-7a33-81ae-cfd2520595f4