Remove RR Sync: Testing

[pcw109550]

Validate the assumption that ELP2P is working as expected, for performing EL Sync to fill in the unsafe gap.

Run a real world/sysgo testing scenario trying to sync using the op-node.

We have multiple combinations:

• syncmode: sync.CLSync / sync.ELSync
• RR Sync enabled / disabled
• EL implementation: geth / reth

Note that we have an assumption that EL P2P connectivity is stable, which means the syncing EL is connected to the EL which is fully synced

Validate the EL side payload caching behavior, and check that if the gaps are filled, the latest payload can be appended to the unsafe chain and become canonicalized, after the initial EL sync run.

Should benchmark and examine how long will it takes to fill in the unsafe gap using real chain. We may directly query the EL using the eth_getBlockByNumber("latest") to check that the EL actually reached the unsafe head tip, not relying on the optimism_syncStatus result from the op-node.

More concretely the testing scenario will be

1. Prepare op-node and EL(with stable ELP2P) which are fully synced, reaching the unsafe tip
2. Shut op-node down.
3. Stay for 5 minutes to make the EL(with stable ELP2P) not advance, intentionally making the unsafe gap
4. Start op-node with
   • RR Sync disabled (via flag)
   • Patched to do the EL Sync to fill in the gap
   • Connected via CLP2P and receiving unsafe payloads from the sequencer
5. Measure time until the EL(with stable ELP2P) reaches the tip.