feat: expose detailed try_finalize_psbt outcomes

[reez]

Description

First step for #73, following ValuedMammal's suggestion.

This PR keeps the scope to PSBT finalization only:

• add try_finalize_psbt which returns FinalizePsbtResult
• report per input outcomes via FinalizePsbtInputResult

Notes to the reviewers

This is now additive rather than breaking: Wallet::finalize_psbt still returns bool

Intentionally not included here:

• changing Wallet::sign to return a richer result type
• any broader redesign beyond the PSBT finalization API surface

Changelog notice

• Add Wallet::try_finalize_psbt, which returns FinalizePsbtResult and exposes per-input finalization outcomes while preserving the existing Wallet::finalize_psbt API.

Checklists

All Submissions:

• I've signed all my commits
• I followed the contribution guidelines
• I ran just p before pushing

New Features:

• I've added tests for the new feature
• I've added docs for the new feature

[codecov]

Codecov Report

❌ Patch coverage is 96.38554% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 81.13%. Comparing base (58fe631) to head (09d2cd0).

Files with missing lines	Patch %	Lines
src/types.rs	82.35%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #433      +/-   ##
==========================================
+ Coverage   80.96%   81.13%   +0.17%     
==========================================
  Files          24       24              
  Lines        5489     5546      +57     
  Branches      247      246       -1     
==========================================
+ Hits         4444     4500      +56     
- Misses        968      970       +2     
+ Partials       77       76       -1     

Flag	Coverage Δ
rust	81.13% <96.38%> (+0.17%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[reez]

Updated per some good feedback from mammal

[ValuedMammal]

I don't think After and Older are doing much good, and would prefer to leave them out of the new implementation if we plan to support try_finalize_psbt into the future.

[notmandatory]

Concept ACK, glad to see this as a non-breaking change.

[reez]

Added four commits as small follow-ups from review feedback from mammal: make finalization cleanup more explicit, preserve opaque PSBT/input metadata, stop the new try_finalize_psbt path from redacting output metadata, and clarify the internal timelock inputs without changing legacy finalize_psbt behavior.

[oleonardolima]

question: are we using this differently ? otherwise, a single Finalized would be enough imho.

[reez]

I see where you're coming from for sure but I do think the distinctions intentional. Finalized would be this call was able to finalize the input, AlreadyFinalized would be the input already had final script/witness data before this call and we skipped it. is_finalized() treats both as success, but I thought preserving that difference was useful since this API is meant to explain what happened per input.

[oleonardolima]

Good, I think I see where you're going. Agree, it's probably useful to have that distinction if it'll be used for upstream users (e.g UX/UI).

[oleonardolima]

cACK 09d2cd0