According to the comment in our code, [Tor is unreliable with picking a circuit after time change](https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-includes/etc/NetworkManager/dispatcher.d/20-time.sh#L171) so we restart it. Is it still the case, or was it an old bug? Restarting tor has several bad consequences: see #18446 for one example. It also had impacts on ~"D:Sponsor08" work, leading us to bring the "always saveconf" approach (see 3be18d9f074a98 and #18303). So avoiding this restart could be valuable. So this issue is about: 1. understanding if Tor is really unreliable with picking a circuit after time change 2. see if a SIGHUP can be enough when this happens