If we log in on deployment 1, then log out and login to deployment 2 and then in the same sessionwe try to log in back to deployment 1, the token is no longer valid. The plugin will associate withdeployment 1 the token from the second deployment.There is an overly complicated block of code inherited from Gateway plugin with multiple fallback sequencesfor both the deployment url and token from multiple sources (secrets store, data dir config, env, etc...).This fix simplifies the approach, we only store the url and the token in the secrets store, the token isalways associated to a hostname. If there is no previous URL to remember (like the first time login) wedefault tohttps://dev.coder.com/ and empty token.

On top of that the shared auth context was reset each time the TBX window was hided and then madevisible again. The auth context is now a singleton object shared between the wizard steps