Handle limited number of entries returned from eth_getLogs RPC call

[marcinczenko]

This is to capture the remark from @AuHau in the context of #922 (direct link to the comment: #922 (review)). Here is a summary of the discussion we had with respect to that comment.

With some RPC providers the number of entries returned by the eth_getLogs RPC call is limited. For example, Infura has a limit of 10 000 results coming back from eth_getLogs call. As a raw estimate, for an average of 4 slots per request, we would hit this limit if our network has an average of 10000 / 4 / 30 = 83 storage requests per day. Also in the Logs in the Linea Scan API documentation we read that:

For performance & security considerations, only the first 1000 results are return. So please narrow down the filter parameters.

On their Network information page, Linea recommends using Infura for the RPC URL, which means that the Infura restriction above may quickly become relevant to us.

Our current resolution is to record the issue (this issue), observe the number of storage requests on the network and when approaching the limit, amend the operations accordingly by experimentally finding a safe number of blocks to look back so that the number of log entries does not exceed the above limit and then using multiple getLogs calls to retrieve the required history.