Handle "conflicted" transactions properly

This introduces the notion of a "conflicted" transaction-- a transaction created by the wallet that is not in either the blockchain or the memory pool, and that (therefore) is unlikely to ever be confirmed.

In the RPC interface, these transactions were previously reported as confirmations : 0 -- with this change, they are reported as confirmations : -1 and category : "conflicted".

So if a transaction is mutated or double-spent, and the mutated version ends up being mined, listtransactions will show both.  Transactions can go from category conflicted to sent/received if a blockchain re-org happens.

This is not intended to be a complete solution to all the malleability issues, but is a necessary first step.