macOS client app looses track of state

I can end up with a "useless" macOS client application -- it's not logged in, and there's no way to get to the login screen. (Originally [mis posted](https://github.com/keybase/client/issues/10148#issuecomment-363213435) as part of another bug.)

Sometimes, a stack trace is displayed on the app's screen (see below).

STR:
1. log into keybase via the app
2. quit the app
3. go to a terminal and logout from CLI
4. start keybase app _not_ from the toolbar (I used Spotlight)
5. app starts on "logged in" screen, no way to get to login.

Workaround:
- login from CLI, or
- Use the Keybase menu bar item (which knows you're logged out and presents a login button)


Start by reproducing the listed sequence: log in through the app, quit it, log out from the CLI, then relaunch the macOS app outside the menu bar. Trace how startup determines login state and compare it with the menu bar behavior; done means the app recognizes the logged-out state and provides a login screen without requiring CLI login.

Written by the indexing model from the issue text.