[AA] fix: bundler relies on eth_getLogs with indefinite range

[souradeep-das]

Issue Type

[X] bug report
[ ] feature request

Current Behavior

L2 does not support eth_getLogs with ranges more than 5000. As a result bundler fails to spin up for test/main networks

error could be of the form

/opt/optimism/packages/boba/bundler/bundler.js:2
...

or

{"jsonrpc":"2.0","error":{"code":-32000,"message":"exceed maximum block range: 5000"},"id":48}\n',
  error: Error: exceed maximum block range: 5000

The reason for the error is here: https://github.com/bobanetwork/boba/blob/develop/packages/boba/bundler/src/modules/EventsManager.ts#L42

Expected Behavior

Bundler starts and runs for networks with eth_getLogs limits

Steps to Reproduce

• change L2_NODE_WEB3_URL on the bundler to point to the test network
• try spinning up the bundler

Suggested Fix

Find a way to accomodate the bundler requests within the specified 5k range

Can use: a local memory counter for the current read counter
and for when it starts the first time/ restarts split it into 5000 block requests