UX papercuts when an oauth token is revoked

[code-asher]

To reproduce:

1. Log in with oauth locally (no remotes opened)
2. With VS Code still open and the Coder sidebar opened, revoke the token from the Coder dashboard

I assume these issues could also happen if the refresh token expired? But not sure how to easily test that.

• The sidebar becomes this half-logged-in state where "my workspaces" is blank and "all workspaces" is populated. To log back in, you must log out first then log in. Instead, we should revert the sidebar to the logged out state where the "log in" button is shown.

• A notification saying to log in with the Coder sidebar appears. We could add a log in button directly to this notification, might be nicer than having to go through the sidebar.

• Sometimes you can get two notifications, that both more or less say the same thing. Could we consolidate them? Personally I like the one in the corner better than the big modal popup one, at least for this scenario.

• When I do log back in, my "all workspaces" view was empty. A manual refresh fixes it, but if I leave VS Code open it never gets populated. We are probably missing an initial call to populate those workspaces after logging back in.

[EhabY]

So we currently have two clients, one for the extension (sidebar), and one for remote which is used for some commands. If we get 401s, should we show a popup dialog or a notification in the corner telling the user to login?

For the extension it's pretty obvious that we can just show the "Login" in the workspaces view so basically the user is logged out + a notification for less friction. But for the remote, having a logged out client could cause issues when certain commands are executed or even the websockets might fail. So in this case do we want a dialog since it's more "urgent" on every 401 OR do we want something similar to extension but it would still show on every 401?