Cardano Updates

Add a test for ensuring that a peer can download all valid TXs when
faced with two peers with conflicting tx order.

In case of duplicate txids, a second invalid tx could be counted as
valid because it was tracked by txid alongside the valid duplicate,
conflating the two.

Add a test for ensuring that a peer can download all valid TXs when
faced with two peers with conflicting tx order.

Add a test for ensuring that a peer can download all valid TXs when
faced with two peers with conflicting tx order.

In case of duplicate txids a second invalid txids could be counted as
valid because it was tracked with txid along

Not only idle peers but all peers should be notified when something
changes for one of their TX.s

Add a test for ensuring that a peer can download all valid TXs when
faced with two peers with conflicting tx order.

When picking TXs to submit to the mempool stop at gaps.
When picking TXs to download use the peer's advertisement order as a
guide, not the TxKey order.

Inline some hot path functions. The old NOINLINE pragmas where a leftover
from V1, and not applicable to V2 since we don't run unsafeNoThunks
between states.

The mempool reader is not used anymore.

Merge prop_handleReceivedTxs_buffersAndDropsOmitted,
prop_handleReceivedTxs_dropsLateBodies,
prop_handleReceivedTxs_penalizesOmittedAfterPrune into
prop_handleReceivedTxs. Improve tests to use arbitrary shared state,
local state and a list of TXs.

Merge prop_handleReceivedTxIds_newEntries,
prop_handleReceivedTxIds_knownToMempool and
prop_handleReceivedTxIds_retainedIsLocalOnly into a single property
based test that exercise all cases.

ChurnMode refactored

This way it's consistent with `PraosFetchMode` constructor.

Use a newtype for `ChurnMode`. ChurnMode follows `FetchMode`, hence
a newtype actually makes more sense than a separate data type.

Bump maxNumTxIdsToRequest to 6 and maxOutstandingTxBatchesPerPeer to 4.

Karknu/bots

Fix the cabal examples so that they work

Handle fd/fdfind differense in run-stylish-haskell.sh just as the other
scripts do.

Use a newtype for `ChurnMode`. ChurnMode follows `FetchMode`, hence
a newtype actually makes more sense than a separate data type.

Move cleanup of expired retained TXs and orphaned TXs to the counter
thread.

Use a newtype for `ChurnMode`. ChurnMode follows `FetchMode`, hence
a newtype actually makes more sense than a separate data type.