feat: support Commit gossiping on P2P level

[tzdybal]

This PR introduces Commit gossiping logic. Only the latest commit is interesting for full nodes (as older ones are available in DA).
Work will be continued in future PRs.

Resolves #479.

[codecov-commenter]

Codecov Report

Merging #486 (cf9367a) into main (2ea2334) will decrease coverage by 0.06%.
The diff coverage is 44.18%.

@@            Coverage Diff             @@
##             main     #486      +/-   ##
==========================================
- Coverage   56.15%   56.08%   -0.07%     
==========================================
  Files          50       50              
  Lines        9237     9278      +41     
==========================================
+ Hits         5187     5204      +17     
- Misses       3292     3314      +22     
- Partials      758      760       +2     

Impacted Files	Coverage Δ
node/node.go	61.11% <11.76%> (-4.22%)	⬇️
block/manager.go	62.35% <62.50%> (+<0.01%)	⬆️
p2p/client.go	62.91% <66.66%> (-0.04%)	⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[Wondertan]

In celestia-node we gossip commit along with headers. Is the separation between those a requirement in Optimint?

[tzdybal]

In celestia-node we gossip commit along with headers. Is the separation between those a requirement in Optimint?

No, it's just how I implemented it now. I just thought this way it will be a bit easier and cleaner (no need to have a separate structure just to serialize/deserialize both, etc). Also, theoretically this way full node may pause receiving commits if it's catching up.

[liamsi]

no need to have a separate structure

The structure already exists fwiw: https://github.com/tendermint/tendermint/blob/d68d25dcd5d6a66aa4f9a67bd79e9f09cee84458/types/light.go#L132-L137