[Bug] Get Block Receipts not working in the latest version

Bug report

Hello,

We just implemented the eth_getBlockReceipts RPC call in our node but we noticed it's not working properly in the latest version of graph-node (using graphprotocol/graph-node:v0.36.1 docker image).

In all implementations of the call the params look like this:

{"jsonrpc":"2.0","method":"eth_getBlockReceipts","params":["0xa4c3c1414373ed64c1b80d007d8edab0335193d87788ebfddc59c79a5feb1ec2"],"id":1}

But graph-node sends this request:

{"jsonrpc":"2.0","method":"eth_getBlockReceipts","params":[{"blockHash":"0xa4c3c1414373ed64c1b80d007d8edab0335193d87788ebfddc59c79a5feb1ec2"}],"id":1}

Guessing the problem is in the rust-web3 fork where the BlockId is serialized directly to json instead of having separate cases for block number and hash - https://github.com/graphprotocol/rust-web3/blob/graph-patches-onto-0.18/src/api/eth.rs#L144

I see there's a change by @incrypto32 here https://github.com/graphprotocol/rust-web3/commit/b9ba7c72316761ae23e95d8d6be1135a5f9e9c01 and that's why I marked this as a regression.

Thanks,

Relevant log output

Graph node:

graph-node-1  | Feb 18 22:19:18.918 WARN Skipping use of block receipts, reason: Error fetching block receipts: RPC error: Error { code: InvalidParams, message: "INVALID_PARAMS: Invalid method parameters (invalid name and/or type) recognised: Type is not convertible to string", data: None }, provider: mainnet-rpc-0, component: EthereumPollingBlockIngestor

Node:
blockchain-taraxa-node-3 taraxa-node {"jsonrpc":"2.0","method":"eth_getBlockReceipts","params":[{"blockHash":"0xa4c3c1414373ed64c1b80d007d8edab0335193d87788ebfddc59c79a5feb1ec2"}],"id":5}

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

• Tick this box if this bug is caused by a regression found in the latest release.
• Tick this box if this bug is specific to the hosted service.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

Linux