In the agent we have the following retry backoff calculation logic:
Since the `Duration` uses `int64_t` to hold nanosecond, if we set the `authentication_backoff_factor` to 1 second, we will overflow after 34 failed authentications (from second to nanosecond we lose 30 bits and 2^34 in the `pow()`).
The effect is we do not backoff at all, we will just retry immediately after the 5s timeout:
The scheduler driver also has the same issue.
We should also audit all the other backoff logic.