Block Range Scanner in Historic and Latest Events Modes Should Expose an Ack-Channel To Calculate the Next Block Range

[0xNeshi]

Currently these two modes run "too fast", meaning the block range scanner finishes it's operation in a matter of milliseconds, while the consumer may take longer to process each block range in turn. This means that when BRS emits a block range it's valid, but by the time the consumer processes it, a reorg could've occurred, which would not be detected, as BRS stops working once it emits all of the block ranges.

Introducing an acknowledgement channel would allow the consumer to give a go-ahead to the BRS to calculate only the next block range, keeping BRS alive and detecting reorgs Just-in-Time.

This would allow us to uncomment these two tests:

• historical_emits_correction_range_when_reorg_below_end
• historical_emits_correction_range_when_end_num_reorgs