Add domain snap sync algorithm

[shamil-gadelshin]

This PR introduces several important pieces for domain snap sync implementation (#3026): snap sync orchestrator and domain snap sync algorithm. This PR continues the discussion on the algorithm implementation highlighting the current decisions. It lacks the final integration in the code both at consensus and domain chain sides, proper configuration changes, and several security guarantees discussed previously.

The first commit introduces the SnapSyncOrchestrator - a synchronization manager that arranges correctly processes in both consensus and domain chains. 2-4 commits modify the existing code and add a structure to pass to the domain snap-sync algorithm introduced in the commit 5. The last (6) commit has an updated Cargo.lock placed separately to simplify the review.

Known future algorithm changes

• change state block acquisition from downloading from remote peers to local derivation from consensus block
• simple acquisition of the last confirmed domain block execution receipt must be replaced with the correct consensus protocol similar to segment headers acquisition
• MMR data should be verified against the state (MMR roots)
• introduce changes for MMR sync algorithm to work with "five segments lag" (see commit 3 and FINALIZATION_DEPTH_IN_SEGMENTS constant): modify MMR gadget to use archived blocks instead of finalized blocks.

Code contributor checklist:

• I have read, understood and followed contributing guide

[teor2345]

Looks good, but I don’t understand the snap sync algorithm enough to fully review it.

[teor2345]

Thanks for the updates, I don't think I'm familiar enough with the algorithm to approve, but it looks reasonable to me.