Implement an exponential backoff retry for unsollicitated token renewal

[NFRBEZ]

Purpose of the feature (why)

From now, when token is not valid, the browser is getting open every 5 min, polluting browser of these windows

Your idea (how)

Implement an exponential backoff retry capped at like 4h, because if there is one unfullfilled unsollicitated attempt in the 5 min, there is very high chance that it would be the same in the next 5 min.

So for example, it could be nice to retry in the next 30 min, then in the next hour, then in the next 4 hour, so there is at most 8 unsollicitated request the first day, then 6 each day follow.
At any time, if the user want to execute a kubectl query, it would imply trigger an authentication request. So from my point of view, these retry mechanisms isn't valuable, but modulating it could be a a nice workaround