After introducing IAM auth integration to lakectl #616
We should extend token caching unit tests to test the following scenarios:
Empty cache
Run some lakectl abuse command (with small number of requests, this is not a stress testing)
Login called only once
We save the token to cache only once
Another lakectl abuse command executed
We get the token from the cache only once
No login performed
Edit the token to an expired one in the cache
perform another lakectl abuse command
validate the call executed as expected
validate that we: tried to get the token from the cache only once, preformed login call only once, saved the new token to cache only once
no login call executed (using cache