Move core application state into the shellModule

[jgaehring]

This would include data and bits of state that are core to the app's basic funtionality, things like whether the user was online or not, error messages, etc. A big question is whether or not user and host details would be included here, or if that would remain part of the login module. The shellModule would certainly not include data about the farm, like the data contained in logs or assets, which are all part of the farmModule in Vuex.

[jgaehring]

Might be nice to add this bit of state back in:

const shellModule = {
  state: {
    // ...
    userInfo: {
      username: '',
      host: '',
      loggedIn: false,
    },
  },
  // ...
}

I removed this from the loginModule a while back, because it wasn't really being used, in favor of better error handling when dealing with authentication. I still think authentication and routing should be determined by handling different HTTP response codes, but this state could be useful information to surface to the user, just so they can verify which server their connected to, what user they're logged in as, etc, along with the option to login/logout.

[jgaehring]

This has been resolved for a little while now, since at least PR #39 .

[mstenta]

(Transferring all issues from old repository. See #92)