Account Login and Tokens

[nickrsan]

Make it so that model runs only happen in the context of a particular user, using their tokens to run the model and associate it with their account.

• [X] Provide users with tokens
• [X] Make token for logged in user available within Stormchaser
• [x] Send token as part of authorization header with requests from stormchaser
• [x] Store token in SessionStorage so that users don't have to log in again after reloading the page (should we use LocalStorage instead?)
• [x] Define model area that user is running and send that as part of request for regions
• [ ] Only return regions if user is a member of a group/organization that has access to run the model area

[nickrsan]

I'm moving some of this up to the current milestone because I'm working on it now and it'll be easier to make everything work by user now than it will be later

[nickrsan]

Still need to change how we set and select the current model area the user is working in. We might want to select a per-user default model area, then have a Django permission that specifies if they're allowed to change their model area, at which point, they see an option in the interface. This is mostly a pretty advanced feature though since in our current deployment plans, installs won't have more than one model area. But we still need to do something to stop hardcoding the organization/model area IDs into stormchaser - it needs to come from the API or a user definition in the application in some way.

[nickrsan]

Implemented Model Area selector for those with access to multiple areas.