feat: use op receiptsFetcher on BlocksReceiptsByNumbers

[ericvelazquez]

Ticket

• Related Linear Ticket: SEQ-182

What does this PR do?

• Summary: Currently we use the non-standard but much more performant "eth_getBlockReceipts" RPC method to get all the receipts for a block. Since this is non-standard however, some RPCs do not support it.
• Key Changes:
  • Adding a receiptsFetcher in the rpc-client struct.
  • This receiptsFetcher is imported from the op source code
  • Removed Config interface. Using the struct instead

Does this PR introduce any breaking changes (API/schema)?

• No

Do any environment variables need to be updated or added before deployment?

• No

How can this PR be tested?

• Unit & integration tests

[linear]

SEQ-182 Implement fallback for getting block receipts

Currently we use the non-standard but much more performant "eth_getBlockReceipts" RPC method to get all the receipts for a block. Since this is non-standard however, some RPCs do not support it

geth has a component with a bunch of logic and fallbacks around getting receipts: https://github.com/ethereum-optimism/optimism/blob/4f1e8a7036e1f85fb1754ca1bb08a461c7c50ac4/op-service/sources/receipts_rpc.go#L61

We should either re-use this component or duplicate some similar logic for if that method isnt available

[jorgemmsilva]

I think this is an excellent change, good catch on the non-standard method being used! 💪

left a few comments about best practices and how we organize the code