Hardware wallet emulator E2E coverage

[ovitrif]

Part of #998.

Split from #1030 so connection reliability and UX polish can stay focused on runtime behavior while this issue owns automated coverage.

Scope

Add hardware-wallet automated test support so the connect and transfer flows can be run by AI agents and in CI without a physical device.

• Audit and add UI test hooks (testTags / accessibility IDs) on the hardware-wallet screens where needed.
• Keep Android journey docs aligned with the current hardware-wallet screen tags and flow names.
• Add a hardware-wallet E2E shard that can run the Connect Hardware flow against a Trezor emulator.
• Drive the E2E path through a Trezor emulator, not a physical device.
• Cover the Transfer to Spending signing path once the emulator/device bridge can exercise it reliably.
• Include coverage for USB and BLE-equivalent route handling where the test environment can model both paths.
• Include regression coverage for locked-device, pairing-code retry, PIN retry, reconnect, and device-busy/backoff behavior once the supporting bitkit-core releases are consumed.
• Include passphrase-enabled wallet scenarios if that UX is supported by the app flow.

Related work

• chore: align trezor dev tooling with ios #1008 tracks aligning Android Trezor dev tooling with bitkit-docker.
• Hardware wallet connection reliability and UX polish #1030 tracks the runtime connection reliability and UX polishing that this automation should eventually prove.
• feat: expose trezor lock state bitkit-core#104 adds lock-state and busy-state support.
• fix: surface typed trezor pin failures bitkit-core#105 tracks typed Trezor PIN failure mapping for mobile bindings.

Acceptance criteria

• Hardware-wallet journeys can be run locally by an agent without a physical Trezor.
• CI has a dedicated hardware-wallet E2E path or shard once the emulator setup is reliable enough for hosted runners.
• Connect Hardware flow coverage includes the happy path and at least one retry/error path.
• Transfer to Spending coverage proves the app reaches and handles the signing path with the emulator.
• Test hooks and journey docs stay aligned with the implemented Compose testTags.