Fixing camel case content types that providers sometimes reply with

Add methods that standardise the response JSON keys into snake cased keys. we tried working with an oauth provider that used the java representation form "accessToken" instead of "access_token".

other thing is that we downcased the content_type header value to match parser matching.