[Bug] legacy address option is not being used for address which have conflicting auth keys

[sasuke0787]

🐛 Bug Report

Describe the bug
The application fails to handle legacy addresses (v5, 16-byte) correctly when performing transactions, particularly for addresses with conflicting authentication keys. This causes transaction failures with errors like "INSUFFICIENT_BALANCE_FOR_TRANSACTION_FEE" or "BAD_CHAIN_ID" even when the account has sufficient balance.

Steps to Reproduce

Reproduction steps:

1. Open Carpe wallet with a legacy account (address that starts with many zeros, using v5 format)
2. Attempt to send a transaction (coin transfer, vouch, or any other transaction)
3. Transaction fails with an error like "INSUFFICIENT_BALANCE_FOR_TRANSACTION_FEE"

[dboreham]

Workaround at present is to use the CLI and specify --legacy-address