Max/add about profile

Not ready to merge, but adds Profile and about pages. Have some questions about how we want to do user loading/rails things.
Okay here's what I'm thinking:

We need the user object for more than just the profile, we need the `currentUser` in order to tell what menu items to display, what features to enable, etc. I can think of two options and I think one is better.

1) We always hit the sign in endpoint such that when we start up, we display some sort of loading screen while we hit the server for the current user.

2) We make some sort of "home" request that the user hits when they open the app. This home request is kind of like the login request, but it batches up a bunch of information that we'll need later on. We're going to need the current user as well as a list of the common assignees (if we decide that tasks can be assigned to actual users cc @melhuang). We'll also want some config stuff (potentially if we want to be legit) and any sort of "beta" features would also come down as flags in this "home" request. 

Thoughts?