[feature suggestion] "--tor inside" option to run ZeroNet in the VM connected to Tor

Currently these options are supported: `--tor {disable,enable,always}`.
`--tor always` is designed to run alongside the Tor process, and means that ZeroNet will use the Tor controller port to create the hidden service and Tor's SOCKS5 port to connect to the peers.

However, people sometimes also run Tor-connected VMs. This is actually the most secure way to connect to the Tor network, see for example the Whonix and Qubes projects. The suggested `--tor inside` option will work the same way as `--tor always` works with these exceptions:
- NetZero will not use SOCKS5, instead it will just connect to all peers directly, and perform DNS queries directly too, dark and clear nets alike.
- NetZero will not use the Tor controller port, instead the HS address and port will be supplied as an additional, required argument, for example `--tor_hidden_service {hs1}.onion:{port1}{:{hs2}.onion:{port2}{:...}}`. User will create hidden service(s) and route it/them to that port(s).

Start by locating the existing `--tor` option and its `always` behavior, then review how the proposed `--tor inside` and required `--tor_hidden_service` arguments would be parsed. Done means supporting the specified direct peer and DNS connections while accepting user-supplied hidden-service addresses and ports; the issue names no files or tests to run.

由索引模型根据 Issue 内容生成。