Today request/response body is always encoded in JSON.
Should accept application/x-www-form-urlencoded too.

1. Define a new field in the custom option to define a list of acceptable encoding of request body
2. Similar field to define the list of possible response body
   • maybe should prefer the same encoding as the request
3. Make the parameter deserialization/serialization pluggable