feat: delete sharedkey if invalid and attempt other auth method

[atadj]

This is related to the issue #251
This is a suggested solution for deleting the shared key if not valid, and then try to authenticate again.

[equinor-ruaj]

Could it be an idea that:
If the SumoClient gets an exception that sharedkey is invalid -> Catch the exception -> Delete the sharedkey -> Raise the exception

I.e. we don´t do any validation up front and we don´t do any special retries and what not. But if we detect that a sharedkey is invalid we delete it before exiting.

In theory it will then "just work" if the user tries again.
Which might also be a bad thing since we can´t track what the issue was then...
@rwiker

[rwiker]

That's a good idea, I think... the code becomes a bit simpler, and we still manage to get rid of the invalid token. We should probably print out something to let the user know that a retry might help.

[equinor-ruaj]

Do you want to give that a go @atadj ?

• If a request gets 401 AND a sharedkeys is being used -> Delete the sharedkey + log something like "Stale Sumo session detected, run again to reset automatically." -> Raise the 401 exception

[atadj]

Do you want to give that a go @atadj ?

• If a request gets 401 AND a sharedkeys is being used -> Delete the sharedkey + log something like "Stale Sumo session detected, run again to reset automatically." -> Raise the 401 exception

I think yes, I can work on it!

[atadj]

I just realised that my commit messages don't respect the semantic commit messages structure 😐, will be better for next commits hopefully

[rwiker]

Not a problem with the commit messages... you'll get a chance to edit the messages if you do a "squash and merge".