Introduce block tracker poll interval

[goran-ethernal]

Description

Some of the clients experienced an issue with block tracker (which is a part of ethgo third party library), where on all validator nodes, it polled rootchain rpc endpoints eth_getBlockByNumber and eth_getBlockByHash each second, causing them to spend all their allowed limit for querying rpc points on a main net such as Ethereum. This sequentially caused all other bridge actions to fail such as state sync events for deposits, or checkpointing. This issue only persisted for block trackers on validator nodes that track the state sync events (which transfer data from L1 to L2).

Block tracker in ethgo has a PollInterval (in time.Duration), which determines how often it calls given rpc endpoints, but it's configuration was not exposed explicitly, so we needed to expand our event_tracker to receive an interval, which then is set to the block tracker through its field.

This PR introduces two new flags:

1. In genesis command - we introduced a new flag --block-tracker-poll-interval, which is defined in time duration (for example, --block-tracker-poll-interval "1s" or block-tracker-poll-interval "12s"). This is part of the genesis command and genesis.json file because, all validator nodes are tracking state sync events. Block proposers are the ones that add state sync commitment transactions at the end of a sprint, while the rest of the validators validate the given transaction, hence all validators need to track state sync events from rootchain. For a state sync commitment transaction to be valid, quorum of validators must be reached, meaning at lest 2/3+1 validators must have the same state sync events tracked. So if we are to set this flag on a server level, that means that each validator can have a different poll time, and will have different number of state sync events tracked at a point of time, which is not a desired behavior.
2. In server command - we introduced a new flag --relayer-poll-interval, which is defined in time duration (for example, example, --relayer-poll-interval "1s" or --relayer-poll-interval "12s"). Since relayer node uses block tracker as well, but for child chain (tracking when a state sync commitment is submitted to child contract), we added this flag, so that the user can configure their relayer nodes as well to poll given rpc endpoints on child chain at desired intervals.

Tagging @DannyS03 to update the documentation.

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in code

Testing

• I have tested this code with the official test suite
• I have tested this code manually

[Stefan-Ethernal]

Generally LGTM