feat(dot/sync): Implement warp sync strategy

[dimartiro]

Changes

Implementation of the warp sync strategy.
This strategy is composed of 2 phases:

1. Request warp sync proofs until get one completed proof (last finalized block)
2. Retrieve that block to be used later for the state sync strategy

This goal of this strategy is to reach the latest finalized block of the canonical chain following authority set changes and validating justifications.
After this block is reached, we have to retrieve its state using the state_sync, that will allow us to build blocks on top of that one while we fill the gap between genesis and the latest finalized block retrieved by the warp sync.

Summary of changes

• Add new warp_sync strategy
  • Add required warp sync p2p messages
  • Add new reputation changes constants
• Refactor peer set view to share the same reference between the strategies
• Add CLI config to use warp sync instead of full sync when node is started
• Tests

Tests

make test

Issues

closes: #3183, #4277, #4268

[EclesioMeloJunior]

LGTM! 🚀

[haikoschol]

just a few nits/questions but LGTM!