Improve the timeout logic of Tor Connection

Tracking here bits of discussion from #18470 (closed). My technical summary might be totally flawed, but I want a place to track this.

If I understand correctly, right now the timeout logic of TCA makes it so that the error screen could be returned on very slow networks even if connecting to Tor is possible.

Ideally, we should have a shorter timeout when "nothing happened" and a longer timeout when "something happens but it's slow". It would improve UX for both people on slow networks (prevent false negatives) and people on fast networks (get faster errors when nothing happens).

I understand that we currently don't make a different between "nothing happened" and "something happens but it's slow", otherwise we shouldn't fallback on an error so quickly when it's still possible to connect to Tor. This might not be possible to improve right now and might require some work at Tor.

I might be totally mistaken and need an update from @boyska on how the timeout currently works.

Blocked by #18539 (closed)