Disable bootstrapping and changes to settings until TorSettings is ready

Spinning off #41907 (closed).

Currently, the bootstrap can start before TorSettings notifies it's ready.

For example, in my Windows VM I have 3-4s to click on connect before this happens:

We've added a workaround to ignore the state change in similar occasions, but this isn't intended to be a definitive solution.

We should instead disable the connect button, or create some intermediate state in which we tell the user we're starting the daemon, or some combination, to avoid the situation described in the original issue but also to do the things properly.

At the moment we are safe because we save the settings also in the torrc, but this might become a need when we switch to Arti.