Feature Request: Add SOCKS5 Proxy Support

[RuoJi6]

Description:
I would like to request the addition of SOCKS5 proxy support in tlsx. Currently, it seems that tlsx does not have built-in support for SOCKS5 proxies, which limits its usability in environments where traffic needs to be routed through a proxy server.

Use Case:
In many scenarios, especially in security testing or network analysis, it is necessary to route traffic through a SOCKS5 proxy. For example:

Anonymity: When scanning targets, it is often required to hide the original IP address by routing traffic through a proxy.

Network Restrictions: In some environments, direct access to certain IPs or ports is restricted, and a proxy is needed to bypass these restrictions.

Integration with Tools: Many security tools and workflows rely on SOCKS5 proxies for seamless integration with other tools (e.g., proxychains, Burp Suite, etc.).

Adding SOCKS5 proxy support would significantly enhance the flexibility and usability of tlsx in such scenarios.

Proposed Solution:
A new command-line flag (e.g., -proxy or -socks5-proxy) could be added to specify a SOCKS5 proxy. For example:

tlsx -u example.com -jarm -proxy socks5://127.0.0.1:1080

This would allow tlsx to route all its network traffic through the specified SOCKS5 proxy.

Additional Context:
Many other tools in the Project Discovery ecosystem (e.g., httpx, nuclei) already support proxy configurations, and adding this feature to tlsx would align it with the rest of the tools.

This feature would be particularly useful for users who rely on tools like proxychains or tsocks but prefer native support within tlsx.

[GeorginaReeder]

Thanks for your feature request @RuoJi6 , we'll take a look into this!