Camel case user record

[btkostner]

Is your feature request related to a problem? Please describe.

Right now, the userInfo endpoint for oauth2 is fetched and saved as is. This is nice, but having to use underscores for some fields (and then turning off eslint) is a pain.

Describe the solution you'd like to see

It would be awesome if we could camel case the user record before save. This could be done in the oauth2 strategy, or add a hook to modify the data before it's saved. Personally, I think the hook idea would save this project from creeping in scope and having to deal with everyone's edge cases.

Describe alternatives you've considered

I'm currently extending the Oauth2Schema class for this functionality.

Additional context

[btkostner]

Also worth adding that if we added a hook for user's to modify the userInfo result before saving, we could drop the user.property setting.