Software wallet integration for transaction legibility on supported hardware wallets

[polymutex]

As per our call on 2025-06-22, one of the things software wallets are currently not rated for is whether or not their integration with hardware wallets enables these hardware wallets to understand the transaction they are signing. As I understand it, the current (sad) state of affairs for hardware wallet transaction legibility requires work on both the software side and the hardware wallet side.

This issue tracks the addition of wallet feature data to track the software side of this problem. The goal is that such feature data accurately describes the level of integration that software wallets have for enabling transaction legibility on the hardware wallets they support.

To make this determination, we should probably have a canonical set of "benchmark" transactions that we use to test with. @PatrickAlphaC has already done the work of identifying such transactions in the context of #161 for calldata decoding support. We should probably use the very same set of transactions here.

[nconsigny]

https://github.com/walletbeat/walletbeat/pull/205

This PR refactors the hardware wallet integration criterion for software wallets