Feature/manage profile

Allow logged in users to view and edit their profile
Just looking at this, it is not at all obvious why the extra logic is needed to tease a boolean value out of a field that really should act like a boolean. In vanilla rails with the database tables set up correctly, this just works. The fact that this doesn't work, is not obvious, and though we caught it in this case, it is almost certain that we will forget to check for this special case in the future.

It looks like the reason that this does not work as expected is b/c attr_encrypted breaks the ActiveRecord magic ... this makes sense b/c we are now using string fields instead of boolean/int(1) fields in the database. If this is the case, then we should override the model accessor method to return a boolean for values that should return a boolean and this helper method should be able to assume that the value is a boolean.

I've created an issue (https://github.com/18F/myusa/issues/176) so that we don't have to hold this PR any longer, but this absolutely should be fixed.