[Bug] Request Param in eth_getBlockReceipts at v0.35.1

[Aliceonly]

Bug report

Hi there, I just noticed that the supporting of eth_getBlockReceipts in v0.35.1 changelog
When I run graph-node v0.35.1 to index local foundry anvil chain, it leads rpc error: number too large to fit in target type

Then I found that the latest version graph-node request eth_getBlockReceipts with block_hash which the rpc only accept block_number as param

I think the indexer should be flexible of those 2 params

Relevant log output

graph-node-1  | Aug 23 15:47:25.356 DEBG Trying again after eth_getBlockReceipts RPC call for block 0x80774fd8c17f0189fb45b61960de6d43e11567933b7f45cc3b645b1c4cb0345d failed (attempt #1) with result Err(Rpc(Error { code: InvalidParams, message: "number too large to fit in target type", data: None })), provider: server-rpc-0, component: EthereumPollingBlockIngestor

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

macOS