Add genesis sync test to CI

[chong-he]

Issue Addressed

• Add e2e sync tests for lookup and range sync to CI #7550

Use existing code from @jimmygchen in #7530 and modify for genesis sync test. Thanks @jimmygchen !

[chong-he]

This PR is ready for review. In this test, we use the minimal preset so that it is faster. The local testnet script is also updated to build for minimal:

The rebuild image -b true (link here) is required or Kurtosis wouldn't start

For 120s stop duration, we trigger short distance sync, the lookup sync. We see in the logs:

DEBUG Created block lookup                          peers: [PeerId("16Uiu2HAkzuo2s4zS8Ab1FVPU1GAue212NT3YhHVRgJwE9S1HQ12J")], block_root: 0x149f7747579266942795085564847f3e903de77524ddb59de3077fae5b238432, awaiting_parent: "none", id: 1, service: "lookup_sync"

For 300s stop duration, we trigger long distance sync, the range sync. We see in the logs:

DEBUG Syncing new finalized chain                   id: 1, component: "range_sync"
DEBUG Sync RPC request sent                         method: "BlocksByRange", slots: 8, epoch: 0, peer: 16Uiu2HAm2pJM6EUvzVtN5JwaKyXBx8DAyg9dSXrNPBc81UCP8WBp, id: 3/2/RangeSync/0/1, chain: 1, service: "range_sync"

All sync completed very fast, under 5s. So I reduce the polling time in the script to 0.5s so that we can see some outputs in the terminal, and set a shorter timeout of 5 minutes.