[Issue] Outfox integration : SOCKS5 proxy ignore outfox flag in config file

[simonwicky]

Describe the issue
A SOCKS5 proxy with packet_type = 'outfox' in the config file will still send sphinx packets.

Expected behaviour
Without any overriding instructions, a SOCKS5 proxy with such a config file should send outfox packets.

Steps to Reproduce
Set up a SOCKS5 proxy with packet_type = 'outfox', and route traffic through it. The debug log will display Sphinx packets being sent.

Issue cause
The run command from the SOCKS5 proxy accepts an --outfox flag. Its presence will cause the config to be overridden and to send outfox packets, which is expected. However, its absence will also cause a config override, and sphinx packets will be sent. This behaviour is not expected and very counter intuitive.

[durch]

We don't seem to have any traffic related properties in the config file, so the package_type in config is not supposed to work, the question is, do we want to add these to the config? cc @mmsinclair , @simonwicky

[simonwicky]

We can already set Poisson process delays, mixing delays, SURBs and cover traffic use in the config file. At least for me, it was really practical to be able to set the packet type in the config file as well.
Note that it already works on the native client and the network requester, since it does not have the --outfox CLI argument.