Track timeout issues leading to lost fees

[cbeams]

v0.6.3 shipped fixes (#1044, #1168, #1169) that should avoid the timeout issues we've seen recently that led to lost maker / taker fees and in turn led to a series of reimbursements (bisq-network/support#1).

I'll use this issue to track any new timeouts (or related issues) that occur in v0.6.3 and beyond, to ensure that we've actually squashed this bug.

Based on the nature of the fixes linked above (esp. #1168), we really should not see any further timeouts of this nature. But still, it'll be good to have this issue around throughout the next release cycle just to make sure, and to have a place to capture problems if they do arise.

[cbeams]

Closing as complete. With v0.6.3 out for five days now, we're no longer seeing any timeout errors causing failed trades. We are, however, seeing transactions show up in arbitration with transactions that never got broadcasted. We're tracking those issues in #1193.