Chore/node sync check (#531)
**Context** When using Mithril on mainnet and the node is fully synced, batches of ~200 blocks are written efficiently. When the node is syncing without mithril, yaci-store processes blocks sequentially, reducing sync performance. In docker-compose setup, Yaci Store currently starts before the Cardano node has fully synced to the tip. This can lead to sync inefficiencies or unpredictable behaviour. The unpredictable behavior is not related to data consistency, as long as blocks already synced by the indexer are not reprocessed. However, during node sync, the chain tip keeps moving, causing yaci-store to switch between sequential and parallel modes, resulting in inconsistent performance. **Tests to Do** - [ ] 1. sync test wtih SYNC=true, MITHRIL=true ***Expected behaviour*** - [ ] Indexer should fully sync without being stuck - [ ] DB, indexer and API should should start once the node is at the tip - [ ] 2. sync test with SYNC=true, MITHRIL=false ***Expected behaviour*** - [ ] Indexer should fully sync without being stuck - [ ] DB, indexer and API should should start once the node is at the tip - [ ] 3. sync test with SYNC=false, MITHRIL=true ***Expected behaviour*** - [ ] Indexer should fully sync without being stuck - [ ] DB, indexer and API should would start together - [ ] 4. sync test with SYNC=false, MITHRIL=false ***Expected behaviour*** - [ ] Indexer should be stuck - [ ] DB, indexer and API should would start together - [ ] Also test the offline mode set SYNC to false