refactor: simplify immature transactions handling

[xdustinface]

We currently keep track of immature transactions/UTXOs in a separate collection and try to re-process them on every new incoming block if they are matured. This seems not really necessary to me and adds a lot extra code and complexity. Instead we can just add them like every other transaction/UTXO and exclude/respect them in the interfaces to get transactions or balances imo. This requires to keep track of the synced height within the managed wallet info like added in #305.

Based on:

• chore: drop unused utxo.rs in key-wallet crate #304
• feat: track synced_height per ManagedWalletInfo #305

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch refactor/immature-transactions

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}