Within connlib, we have many nested state machines. Many of them have internal timers by means of timestamps with which they indicate, when they'd like to be "woken" to perform time-related processing. For example, the Allocation state machine would indicate with a timestamp 5 minutes from the time an allocation is created that it needs to be woken again in order to send the refresh message to the relay.

When we reset our network connections, we pretty much discard all state within connlib and together with that, all of these timers. Thus the poll_timeout function would return None, indicating that our state machines are not waiting for anything.

Within the eventloop, the most outer state machine, i.e. ClientState is paired with an Io component that actually implements the timer by scheduling a wake-up aggregated as the earliest point of all state machines.

In order to not fire the same timer multiple times in a row, we already intended to reset the timer once it fired. It turns out that this never worked and the timer still lingered around.

When we call reset, poll_timeout - which feeds this timer - returns None and the timer doesn't get updated until it will finally return Some with an Instant. Because the previous timer didn't get cleared when it fired, this caused connlib to busy loop and prevent some(?) other parts of it from progressing, resulting in us never being able to reconnect to the portal. Yet, because the event loop itself was still operating, we could still resolve DNS queries and such.

Resolves: #7254.