[1572] Convert User Profile to React

[esoterik]

Resolves #1572.

This isn't 100% ready, but I think it's at a good point for someone else to look this over. Currently the "basic" (excluding login info, role, requirements, etc) user attributes are editable from the show with no reload!

Running npm i should install all of the required npm packages; run foreman start -f Procfile.dev instead of rails server.

Tests currently fail on Travis (see this discussion that I just found); I'm looking into fixing it.

I'm planning on converting the whole page except for the reservation history to JS in this issue. I'm not sure what should be done about the other user attributes--should they be left on a separate page because they're more sensitive? I'm not sure how to require a password for changes, either, but these are pretty basic ones so I figured that losing the password requirement isn't a big deal.

I'm also not super sure of how the JS is organized. I think I like the organization by resource better than the typical JS organization of organizing by file type (reducer/component/container/etc), and there's not really a community standard.

I've also enabled ESLint in Hound on this branch; I'm expecting lots of comments. Nevermind, it seems like it uses the config on master regardless, I've moved the config to #1577.

Edit
I've also only tested this in Firefox v46.0.1; I'm going to start testing in Chromium as well

[esoterik]

Okay, the reservation counts on the profile have been moved to react!

[esoterik]

Todo:

• Install/configure ESLint
• Refactor and use action creators
• Fix Travis
• Make sure reducer actions are named in a way that won't cause conflicts later
• Figure out the best way to write tests before I create a monolith

[esoterik]

this and all functions like this can be simplified:

const mapStateToProps = (state) => ({
    user: state.user,
});

[esoterik]

also, note that with how the webpack server runs, we lose access to pry; I'm not sure how to fix that quite yet