Implement Secure Sync

[nazar-pc]

Once we have Defined initial secure sync spec, we need to implement it.

• Make user restart if the node discovers it has synced on the wrong chain
• Change parameters: DSN connects up to 20 peers and decide based on largest subset #1516

More changes might be necessary if written spec has more updated on top of what we have discussed previously.

Background information: https://www.notion.so/subspacelabs/Define-Secure-Consensus-Chain-Sync-Protocol-bba1a73e8ba949cea413eb7dc5281173

[nazar-pc]

@dariolina do you remember what do we mean here exactly? Node will already get stuck if it syncs onto the wrong chain and unable to move forward. If it is on the wrong fork however, it will not be able to objectively tell that it is on the wrong chain, at least not by default.

Looks like it is a non-actionable task so far.

[dariolina]

IIRC we wanted if the node later discovers a heavier chain than its own to present an error to the user, so they wipe and start over. If you would like to refresh your memory we have discussed it in this session at ~2:29:00. An the whole sync discussion started around 02:00:00