eth/filters: eth_getLogs fast exit for invalid block range

[jsvisa]

We can quickly exit if the from > to in eth_getLogs request.

BTW, currently for eth_newFilter, if from>to, then the RPC returns an error, but no error for eth_getLogs, should we need to unify their behavior, or let it go?

eth_getLogs request

{
  "jsonrpc": "2.0",
  "method": "eth_getLogs",
  "id": 74,
  "params": [
    {
      "toBlock": "0x1",
      "fromBlock": "0x2000"
    }
  ]
}

eth_getLogs response

{
  "id": 74,
  "jsonrpc": "2.0",
  "result": []
}

eth_newFilter request

{
  "jsonrpc": "2.0",
  "method": "eth_newFilter",
  "id": 73,
  "params": [
    {
      "toBlock": "0x1",
      "fromBlock": "0x2000"
    }
  ]
}

eth_newFilter response

{
  "error": {
    "code": -32000,
    "message": "invalid from and to block combination: from > to"
  },
  "id": 73,
  "jsonrpc": "2.0"
}

[holiman]

Seems reasonable to me, some nits though

[jsvisa]

Seems reasonable to me, some nits though

@holiman fixed it, please take another look.

[s1na]

Blocked on ethereum/execution-apis#480 being merged.

[ghost]

@s1na @jsvisa Could you generalize the error message? Would like to implement block range limit for eth_getLogs call after this PR is merged just like this one paradigmxyz/reth#5243

Something like invalid block range params would be good

[s1na]

Something like invalid block range params would be good

@kaliubuntu0206 I think this error message would work for us too. However generally I'd like if we could standardize error codes instead of error messages. It's perfectly reasonable that clients would return different messages (e.g. some with more context or less).