WIP: Pooled transactions exchange protocol

[digorithm]

Work in progress

Scope and design

Partially closes #1049. I say partially because this work will be split into two:

1. An initial pooled transactions "handshake" between two newly connected peers, where these two peers will share their pooled transactions. This is the scope of this PR. Then, in a follow-up PR:
2. Another sub-service will periodically request pooled transactions from a random, small subset of known peers and compare and share their pooled transactions like the first part of the protocol.
3. More details in the RFC.

These two combined will lead to the mempool being more resilient.

Tasks and TODOs

• Create and organize the new TxPoolSync service under the current architecture;
• Setup the communication between the new service and the main transaction pool service, and the p2p service (the majority of this work falls under this task);
• Implement the pooled transaction sharing
  • Current blocker: node gets penalized and disconnected when sending transactions
• Write new tests
• Fix old tests and CI-related stuff broken due to these changes;
• Clean-up code (TODOs, improve quality, etc.)
• Write more documentation;

[bvrooman]

To make things a bit easier to review, is it possible/feasible to separate out the nonfunctional formatting changes into a separate PR?

[digorithm]

To make things a bit easier to review, is it possible/feasible to separate out the nonfunctional formatting changes into a separate PR?

Yup, I'll revert those; those were automatically done by my editor + my current version of the formatter. I'll do it asap