Extend documentation of tx-Submission design choice

[coot]

trafficstars

In particular:

The design choice that the tx-submission protocol forwarding transactions, while chain-sync and block fetch download data works very well when the consensus decides that we the remote peer is too far behind: at the same time we are not interested in sending tx to that peer, since it's very unlikely that they would be adopted by the remote peer.