eth_call and eth_estimateGas only return encoded revert reason

[matthew1001]

Description

When eth_call or eth_estimateGas result in execution reverted the error response contains the reason for the revert, ABI-encoded in the data field, e.g.

{
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
        "code": -32000,
        "message": "Execution reverted",
        "data": "0x08c379a00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000002645524332303a207472616e7366657220616d6f756e7420657863656564732062616c616e63650000000000000000000000000000000000000000000000000000"
    }
}

Other clients (Quorum is the specific example I've tried) return the ABI-decoded reason as well. This is particularly convenient for reading revert reasons from application-side logs since a capture of the JSON/RPC flows can show you the cause of a problem without needing to decode the error. Given that the ABI-encoded reason is available it's a very small CPU overhead to perform the conversion in Besu, and the additional network traffic is pretty minimal as well.

Acceptance Criteria

Submit an eth_call or eth_estimateGas that causes execution reverted. The ABI-decoded text is included in the message part of the error response, after the "Execution reverted" prefix. The ABI-encoded data field is also included in the response. If there is no revert reason available, the message field remains as "Execution reverted" which is the existing behaviour.