Implement a chain rebroadcast mechanism independent of GPBFT

[masih]

As part of #792 the propagation of EC Chain is separated into its own pubsub topic, managed via chainexchange. Initially, the broadcast of chain and its reboradcast is coupled to GPBFT broadcast/re-boradcast: Whenever GPBFT broadcasts a message we broadcast its chain and so on. But we can do better, because: all chain subsets can be inferred from the longest broadcasted chain (i.e. the QUALITY proposal), and depending on the progress it may not be necessary to rebroadcast the chain.

Ideally, the system should have control over the chain broadcast intensity. Separate out the heuristic of chain broadcast from GPBFT.

Ideas:

• Only broadcast a chain a fixed number of times.
• Introduce an incrementing sequence number in messages to work around gossipsub deduplication.
• For safety rebroadcast subsets of the QUALITY chain relative to progress?
  • Or just stick with always broadcasting the QUALITY proposal. Because from it we can infer all the sub chains that could be stemmed from it during an instance, and it is simpler to implement/maintain.