Conflicted transactions should not go to wallet history...

[skironDotNet]

result of #2614

If you have 2 wallet files, one is updated one is not, after loading old wallet without "keypool refill" the client my not capture the fact change has been spent. When you try to spent that change you'll see

But the bug is that after clicking OK it then is registered on the wallet history as "conflicted"

Expected behavior would be, don't add it to wallet history as tx could not commit due to double spent. Makes no sense to show it as "confliced" it should just not be processed by the wallet