allow normal swap path even beyond inaction timeout

[chappjc]

Consider TakerSwapCast, where the maker fails to redeem by inaction timeout, but the maker still wants to redeem. Client currently will not do this if the match is revoked, instead waiting until refund. The taker can deal if maker does redeem after revoke, but that's not currently intended operation, and the server will on longer relay the maker's redemption data to the taker once the match is revoked and removed from the Swapper. We should consider ways to allow matches to keep the normal negotiation path operational after revoke, although the at-fault user would still be penalized.

[chappjc]

In addition to facilitating this both client and server side, a partial reward to the client-at-fault's score should be considered to incentivize at least acting late.

Also, in addition to the TakerSwapCast status where there is a late redeem, similar late action could be done with MakerSwapCast where the taker broadcasts their swap late. This would require a little more care to ensure it's not being broadcast with insufficient time for it to reach swapConf before the contract expires.

[chappjc]

Starting to investigate this myself.