Fix tor-has-bootstrapped semantics on network reconnect

It seems that it returns true before tor has reconnected to the Tor network.

“what the test suite needs is something that tells whether Tor currently thinks it should be working (be able to build circuits)”

I wonder if it happens in normal conditions, that is without restoring snapshots. But let me not try to pretend it’s not on my plate ;)
I bet that once we’ve reached tails-tor-has-bootstrapped.target it never gets reset to non-active.
Which, I mean, is a matter of semantics. It currently means: “Tor has already bootstrapped once on this system”.
I wonder if this is buggy in supported non-test-suite case, e.g. on network reconnect. Or if we’re back to “please, test suite folks, tell me what semantics you need from that program”.
maybe we should just restart tails-wait-until-tor-has-bootstrapped.service on network reconnect (not sure if it puts the target back to inactive state)

Feature Branch: bugfix/10732-sanest-tor-has-bootstrapped-semantics

Related issues

• Blocks #7563 (closed)

Original created by @intrigeri on 10732 (Redmine)