Append ABI-decoded revert reason to message field in error responses

[matthew1001]

PR description

Todo:

• eth_call unit tests
• eth_estimateGas unit tests
• Changelog

This PR does the following:

• Adds a helper function to JsonRpcErrorResponse to decode revert reasons
• Adds a private member variable reason to JsonRpcError which can optionally be set
• Appends the reason to the response from JsonRpcError.getMessage() so that whenever the message for a JSON RPC error is retrieved, any reason that is set is included e.g. Execution reverted: ERC20: transfer amount exceeds balance

Note: this is proposed as a change to existing behaviour. I have assumed (rightly or wrongly) that existing applications will most likely use startsWith("Execution reverted") or other language equivalent, to parse error responses today. The fact that Quorum returns errors in this format (and that there isn't an option to exclude the decoded reason) suggests that any application not using startsWith semantics for error parsing is already brittle to different ethereum clients. It could be made configurable in Besu (perhaps with a --exclude-decoded-reason or similar option) but my personal view is to treat this as a fix to existing behaviour and document it in the changelog accordingly. I'm open to other opinions on this from reviewers.

Example error response before this PR:

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

Example error response with this PR:

{
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
        "code": -32000,
        "message": "Execution reverted: ERC20: transfer amount exceeds balance",
        "data": "0x08c379a00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000002645524332303a207472616e7366657220616d6f756e7420657863656564732062616c616e63650000000000000000000000000000000000000000000000000000"
    }
}

Fixed Issue(s)

Fixes #5705

[github-actions]

• I thought about documentation and added the doc-change-required label to this PR if updates are required.
• I thought about the changelog and included a changelog update if required.
• If my PR includes database changes (e.g. KeyValueSegmentIdentifier) I have thought about compatibility and performed forwards and backwards compatibility tests

[matthew1001]

Working through a failing unit test that passes locally...

[siladu]

LGTM - thanks for the detailed PR description 👍

[siladu]

Is the "Error(string)" prefix Besu-specific or in a spec?

[matthew1001]

This is an ethereum standard for the way revert reasons are encoded.