JsonRpc standardization: wrongTransactionNonce error

[yerke26]

Currently eth_call, eth_simulateV1, eth_estimateGas, eth_sendRawTransaction, eth_sendTransaction returns in Geth and Nethermind different error message for the same error:

Nethermind has:

{
    "jsonrpc": "2.0",
    "error": {
        "code": -32000,
        "message": "wrong transaction nonce"
    },
    "id": 1
}

Geth:
when nonce high

{
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
    "code": -32000,
       "message": "err: nonce too high: address {senderAddress}, tx: {txNonce} state: {stateNonce} (supplied gas {gasLimit})"
}

when nonce low:

{
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
    "code": -32000,
       "message": "err: nonce too low: address {senderAddress}, tx: {txNonce} state: {stateNonce} (supplied gas {gasLimit})"
}

replaced WrongTransactionNonce error with TransactionNonceTooHigh, TransactionNonceTooLow

Changes

• List the changes

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Notes on testing

Optional. Remove if not applicable.

Documentation

Requires documentation update

• Yes
• No

If yes, link the PR to the docs update or the issue with the details labeled docs. Remove if not applicable.

Requires explanation in Release Notes

• Yes
• No

If yes, fill in the details here. Remove if not applicable.

Remarks

Optional. Remove if not applicable.

[yerke26]

should change WRONG_TRANSACTION_NONCE logs also?

[LukaszRozmej]

Why not

[LukaszRozmej]

Why not

[MarekM25]

Think about covering with tests