Enhance Juno's rollback mechanism in case of reorg

[wojciechos]

During a blockchain reorganization, Juno currently waits until the sequencer reaches Juno's current block state before beginning to roll back blocks. This delay can result in Juno returning outdated data for extended periods.

Suggested Solution

Initiate Juno's rollback process as soon as its latest block number exceeds the feeder's latest block number. This proactive approach aims to minimize the duration Juno operates with outdated or incorrect block data during reorganization events.

Benefits

Quicker response to reorg events, reducing the time Juno operates with outdated data.