Ensure tor starts at boot.

When you include `SocksPort 9051` in `/etc/tor/torrc`, running `tor` after a reboot (without the `systemd` job, without the `crontab -l` job) the `torsocks ssh` command says: `connection refused` immediately, like there is no tor service running.

If you remove the `SocksPort 9051` line after reboot from `/etc/tor/torrc`, the `torsocks ssh` command does work (after running `tor`).

However, if you remove the `SocksPort 9051 from `/etc/tor/torrc` the installation does not work.

- [ ] resolve this issue, and ensure that the installation works, and that after the reboot running `tor` allows one to ssh into the device.
- [ ] Afterwards restore the `cronjob` of the isolated file and ensure tor starts at boot.

## Issue
If you do not include the `SocksPort 9051` then you can only ssh with torsocks into the onion domain from the virtual machine itself, and not from another/host/parent device. If you do add the `SocksPort 9051` and start tor (with sudo?) then you can ssh into the virtual machine with:
```sh
torsocks ssh -p 9051 @
```