p2p/conn: large (or a lot of) outgoing messages from other reactors can block consensus reactor from making progress #5816
Description
See #5796 and #3920 (comment)
What happened
Large messages (or many messages) produced by other reactors and scheduled to be send can temporarily block consensus reactor from making progress.
Why do you think it happens?
Either libs/flow library does not perform as expected or p2p/conn/connection scheduling logic is invalid.
What did you expect?
No halting. Tendermint top priority is exchanging votes and making blocks with a few transactions + evidence (if any). Consensus reactor messages should have a top priority, while other (e.g. mempool gossip, evidence) should have a lower priority.