Feature request: authentication support for proxies

[anthonybilinski]

Carrying over from irungentoo#1268.

Clients have gotten requests to support authenticated proxies, e.g.:
JFreegman/toxic#371
qTox/qTox#1286

I recognize that as nurupoo mentioned the authentication isn't encrypted with SOCKS5, but we've still had a few duplicate issues for qTox alone, and at least corporate proxies seems like a reasonable use case.

[emdee-is]

There's not much work involved in negotiating authentication in SOCKS.
It would mean adding SOCKS_USER and SOCKS_PASSWORD fields to the ToxOptions. Ideally the iterate code should recheck the authentification and reauthenticate if necessary as corporate proxies often have short timeouts.

You should add support for a comma seperated list of IP:port for NO_PROXY.

[iphydf]

#1683

[emdee-is]

@iphydf Great I missed that. Can you add a comment to the PR the say what the state of the PR is and what it needs to be merged?

Once it lands I can easily modify my testrunner to support SOCKS username and password https://git.plastiras.org/emdee/toxygen_wrapper/src/branch/main/src/tox_wrapper/tests/tests_wrapper.py