fix: no Debug on Display implementations

[luisschwab]

Description

This PR removes the use of debugs on Display implemetations.

Changelog notice

• Implement Display for KeychainKind.
• Implement Display for LoadMismatch.
• Add error message for CreateWithPersistError.
• The CreateTxError::LockTime arm had requested and required inverted, now fixed.
• Remove debugs.

Checklists

All Submissions:

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

[coveralls]

Pull Request Test Coverage Report for Build 15148522315

Details

• 0 of 85 (0.0%) changed or added relevant lines in 4 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.7%) to 85.332%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
wallet/src/wallet/error.rs	0	3	0.0%
wallet/src/types.rs	0	5	0.0%
wallet/src/wallet/mod.rs	0	32	0.0%
wallet/src/wallet/persisted.rs	0	45	0.0%

Totals
Change from base Build 15144463728:	-0.7%
Covered Lines:	7266
Relevant Lines:	8515

---

💛 - Coveralls

[110CodingP]

nit: should we consider changing fmt::Display::fmt in the Display impls of LoadWithPersistError and FileStoreError to use write! for consistency in style?

[110CodingP]

ACK 6e521c9 (compiled the code and ran the tests)

[oleonardolima]

cACK 6e521c9

[luisschwab]

nit: should we consider changing fmt::Display::fmt in the Display impls of LoadWithPersistError and FileStoreError to use write! for consistency in style?

No, because we're using the Display implementation of the underlying types directly.

[luisschwab]

Rebased with suggestions from @ValuedMammal on changeset_info() implementation.

[ValuedMammal]

ACK 0d8d0ec

[evanlinjin]

ACK 0d8d0ec

Just a small nit.

[luisschwab]

Rebased to trigger CI.

[notmandatory]

utACK 3c00f1a