feat: gracefully handle commit/finalize genesis batch event

[yiweichi]

This PR add feature to gracefully handle commit/finalize genesis batch event.

• set the mainnet/sepolia start block number to the one we commit genesis batch
• skip event commit/finalize genesis batch, since it was already persisted default empty batch in db.

corresponding issue: #369

[codspeed-hq]

CodSpeed Performance Report

Merging #383 will not alter performance

_{Comparing feat-gracefull-handle-commit-genesis-batch-event (43f0005) with main (1146460)}

Summary

✅ 2 untouched

[greged93]

just a note here: the genesis batch isn't persisted to DB, we persist a default empty batch. However, the genesis batch commits to the genesis of the chain, which we already have in the EN.

[frisitano]

I'm a little concerned that we are adding additional computational overhead in the statement for no functional difference in processing:

                    .filter(|decoded| !decoded.data.batch_index.is_zero())

[yiweichi]

I'm a little concerned that we are adding additional computational overhead in the statement for no functional difference in processing:

                    .filter(|decoded| !decoded.data.batch_index.is_zero())

Claude says the computational overhead is minimal, shouldn't bring performance issue for L1 watcher at all. And we kinda need this filter to skip genesis batch commit event.

I can move the filter logic above notifications.push(L1Notification::BatchCommit(BatchCommitData {, but this look more elegant.

[frisitano]

lgtm