fix(wallet): added the validation of UTXO data for build_fee_bump

[ItshMoh]

Description

It fixes the Issue bitcoindevkit/bdk_wallet#51 . In this PR we are checking the size of the prev_tx.output list for ensuring that it contains the output referred by each input of the transaction to be bumped.

Notes to the reviewers

here prev_tx.output size is checked. Also changed the .map form .and_then for proper handling of Result.

Checklists

All Submissions:

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

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

[ItshMoh]

Hey @ValuedMammal for This PR. Is the new error variant suitable. Or I should look for existing error variants as you have suggested with #1911 . What do you suggest?

[aagbotemi]

Hey @ItshMoh. you've done a great job working on this PR.

I will suggest you add some unit tests to cover your new implementation. This will help ensure that edge cases, such as validation UTXO data, are handled correctly. Thanks!

[luisschwab]

Hey @ItshMoh, this PR needs to be closed and moved to the new bdk_wallet repo. Here's how:

1. From your Github account, fork https://github.com/bitcoindevkit/bdk_wallet
2. From your local system bdk repo folder, push your PR changes to your bdk_wallet fork on Github:

   git checkout <PR branch path>
   git push git@github.com:<username>/bdk_wallet.git
   

3. Clone to your forked bdk_wallet repo to your local system and switch to your PR branch:

   git clone git@github.com:<username>/bdk_wallet.git
   cd bdk_wallet
   git fetch origin <PR branch path>
   git checkout -b <PR branch path> FETCH_HEAD
   git rebase master
   

4. Resolve rebase conflicts (if any)
5. Force push your PR branch: git push origin -f
6. Create new PR in bitcoindevkit/bdk_wallet repo from your fork branch
7. Copy/paste title and description from your original bdk PR and add a link back to it in your new PR.
8. Close original PR with comment that includes link to new PR.

[evanlinjin]

@ItshMoh since there is no reply for a few weeks, I will be closing this PR.