Fix sqlite database set_utxo to insert or update utxos

[notmandatory]

Description

This PR fixes #591 by:

1. Add sqlite MIGRATIONS statements to remove duplicate utxos and add unique utxos index on txid and vout.
2. Do an upsert (if insert fails update) instead of an insert in set_utxo().
3. Update database::test::test_utxo to also verify set_utxo() doesn't insert duplicate utxos.

Notes to the reviewers

I verified the updated test_utxo fails as expected before my fix and passes after the fix. I tested the new migrations using the below bdk-cli command and a manually updated sqlite db with duplicate utxos.

cargo run --no-default-features --features cli,sqlite-db,esplora-ureq -- wallet -w test1 --descriptor "wpkh(tpubEBr4i6yk5nf5DAaJpsi9N2pPYBeJ7fZ5Z9rmN4977iYLCGco1VyjB9tvvuvYtfZzjD5A8igzgw3HeWeeKFmanHYqksqZXYXGsw5zjnj7KM9/*)" sync

Checklists

All Submissions:

• I've signed all my commits
• I followed the contribution guidelines
• I ran cargo fmt and cargo clippy before committing

New Features:

• I've added tests for the new feature
• I've added docs for the new feature
• I've updated CHANGELOG.md

Bugfixes:

• This pull request breaks the existing API
• I've added tests to reproduce the issue which are now passing
• I'm linking the issue being fixed by this PR

[danielabrozzoni]

I discussed a bit with @afilini about this, while theoretically the duplicated lines should contain the same info, we can't be so sure about that...
If the duplicated lines contain different info (for example: same outpoint, different is_spent), we might end up in an inconsistent state.
Alekos suggested wiping the entire db.
I suggested wiping it only if we find some duplicated outpoints with the different info - if this can be done in a single SQL query (should be doable, but I'm not entirely sure). What do you think?

[notmandatory]

But I'm so proud of my little SQL de-duplicating! haha, anyway, rather than risk an inconsistent state I'll update this to always wipe the database, it's only a cache after all. And I have to agree with @afilini to wipe the data even if there are no dups since either way we will need to warn users that it MIGHT be wiped on this release and they'll need to be prepared to handle it with a sync() (and any reasonable app will do a sync at startup).

[notmandatory]

I force-pushed 154b10b to DELETE all data from tables (except for script version table). Tested locally with bdk-cli and verified MIGRATIONS scripts all run and able to re-sync after. I also added a warning in the CHANGELOG that anyone using the sqlite-db feature will need to do a wallet.sync().

[notmandatory]

This is now ready to go, I also added a fix for our blockchain integration tests in CI that haven't been running.

Once this PR is merge I'm going to cherry pick it into a 0.18.1 fix release since @thunderbiscuit's SoB mentee found that our latest bdk-kotlin (and also I'll guess bdk-swift) release is broken, duplicating balances, because they use the SQLite DB.

[danielabrozzoni]

utACK 35feb10 - Code looks good, but I didn't do any local test to see if the db gets wiped

[notmandatory]

Thanks for the utACK @danielabrozzoni, I'm going to merge now, should be good based on my manually testing, as discussed on the call this is what I did with the unreleased master branch version of bdk-cli:

1. Sync'd with dependency bdk 0.18.0 and new sqlite-db feature enabled:

cargo run --no-default-features --features cli,electrum,sqlite-db -- wallet --descriptor "wpkh(tpubEBr4i6yk5nf5DAaJpsi9N2pPYBeJ7fZ5Z9rmN4977iYLCGco1VyjB9tvvuvYtfZzjD5A8igzgw3HeWeeKFmanHYqksqZXYXGsw5zjnj7KM9/*)" sync

2. Manually checked sqlite DB file tables, verified old schema is there with utxo data, I used database tool in AndroidStudio but can also use sqlite cli tool
3. With same build of bdk-cli got wallet balance, sync'd wallet again and checked balance again, show's double utxos
4. Changed bdk-cli Cargo.toml dependency for bdk to this PR branch version
5. Re-sync'd with bdk-cli and verified correct balance
6. Manually checked sqlite DB tables again, verified new schema is there with new utxo unique constraints and no duplicates

[danielabrozzoni]

Post-merge ACK 35feb10