Fix handling of json rpc errors that use "details" instead of "message"

[eranrund]

Motivation

I ran into an issue when using the RetryClient with a Polygon Mumbia RPC endpoint (https://rpc-mumbai.maticvigil.com/). The error it returns looks like this:
{"error":{"details":"Bad parameters in JSONRPC request: eth_getLogs.","code":-32005},"jsonrpc":"2.0","id":19}

Without this change the JsonRpcError fails to deserialize and the retry logic that is dependent on the JSON error code does not run.

Solution

Make the deserialization a bit more flexible, and have it support both "message" and "details".

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

Thank you!

[DaniPopes]

cc @mattsse @prestwich
Is this right? Can we add this to Alloy?

[mattsse]

this looks more like a server error because this is off spec:

https://www.jsonrpc.org/specification#response_object

[prestwich]

this looks more like a server error because this is off spec:

agree with this. but is the wrong version widely deployed enough to warrant supporting it? 😮‍💨