refactor: use core hw activities

[ovitrif]

Closes #1029
Refs #998

Description

This PR:

1. Replaces separate in-memory Trezor transaction handling with wallet-scoped activities and transaction details persisted by bitkit-core 0.4.0.
2. Derives stable hardware wallet IDs through bitkit-core using enum-backed wallet types, then preserves that wallet scope across watcher events, activity reads, tags, details, seen state, boost lookups, filters, navigation, and Explore.
3. Reconciles each full watcher snapshot with Core before publishing UI state, preserves transfer metadata, and serializes watcher start, persistence, removal, and purge so stale or removed wallet rows cannot return.
4. Keeps transfer-to-spending as one correctly labelled hardware-wallet activity from pending through confirmation, including when another wallet contains the same transaction ID.
5. Purges wallet-scoped activity data when a paired device is removed and rebuilds its history after re-pairing.
6. Retains the current Trezor busy, retry, and cancellation behavior from master and allows on-device confirmations to complete within the Bridge signing timeout.

Preview

No visual redesign. Existing Home, Activity Detail, tag filtering, and Explore surfaces now render wallet-scoped hardware activities from bitkit-core.

QA Notes

Manual Tests

• 1. Settings → Hardware Wallets → pair a Trezor with a seed distinct from the app wallet: the connected hardware wallet appears on Home.
• 2. Fund at least two hardware wallet addresses with different amounts → mine a block: Home shows one blue hardware activity for each transaction.
• 3. Home → Show All → switch Received, Sent, and All tabs: each hardware activity appears only in the matching views and ordering remains correct alongside app activities.
• 4. Hardware activity → Activity Detail → add a tag → back → filter by that tag: the scoped activity remains visible; Explore shows its transaction ID, inputs, and outputs.
• 5. Transfer Funds → enter an amount → approve Recipient, Amount, Locktime, and Summary on the Trezor within 120 seconds → immediately tap Continue Using Bitkit within five seconds: Home shows one pending blue Transfer / From Savings activity.
• 6. Pending transfer → Activity Detail → Blocktank Regtest → mine one block → reopen Activity Detail: the same row is confirmed and Spending increased by the transferred amount.
• 7. Settings → Hardware Wallets → remove the paired device: its activities disappear; re-pairing rebuilds its confirmed history without duplicate rows.
• 8. regression: app on-chain and LN activities → Activity Detail, tags, filters, and Explore: behavior matches master.

Automated Checks

• Unit tests modified: HwWalletRepoTest.kt, ActivityRepoTest.kt, and TransferRepoTest.kt cover wallet-scoped watcher ownership, canonical persistence, persistence recovery, watcher/removal races, transfer reconciliation, and removal purge behavior.
• Unit tests modified: TrezorRepoTest.kt, TrezorBridgeTransportTest.kt, TrezorViewModelTest.kt, and TrezorExceptionExtTest.kt cover Core-derived identity and Trezor transport, retry, busy, cancellation, and signing behavior.
• Unit tests modified: ActivityListViewModelTest.kt, ActivityDetailViewModelTest.kt, TransferViewModelTest.kt, and AppViewModelSendFlowTest.kt cover wallet-scoped filtering, boost relationships, detail routing, tags, and transfer metadata.
• Hardware wallet journeys updated: activity-blue-icons.xml, activity-detail-hw-tags.xml, transfer-to-spending.xml, and its fee/warmup variants cover multiple transactions, hardware activity UI, the complete signing sequence, pending state, same-backend mining, and confirmed state.
• Product-level verification: the Bridge-backed Trezor emulator exposed multiple hardware activities, reconciled stale rows from a full watcher snapshot, persisted a hardware tag, rendered Explore inputs/outputs, signed Transfer To Spending, showed exactly one pending hardware transfer before mining, and kept that same wallet-scoped row confirmed after mining without a default-wallet duplicate.
• Local verification: just compile, just test, and just lint passed; all hardware-wallet journey XML files passed xmllint.

[ovitrif]

Status update:

• This PR now consumes bitkit-core 0.3.9.
• Local verification passed on c0274e311: just compile, just test, and just lint.
• There are no unresolved review threads currently open.
• Coordination note: feat: bump core to 0.3.9 and hw reliability #1062 touches much of the same Core/HW wallet surface. I’d recommend keeping this PR as the base for the Core hardware-activity refactor, then rebasing or splitting feat: bump core to 0.3.9 and hw reliability #1062 afterward so the hardware reliability fixes stay separately reviewable.

[ovitrif]

Decouple UI from persist — update watcher state even if Core persist fails; log error separately.

Addressed this Android-side gating issue: watcher state now updates before Core persistence, so the Trezor balance/activity UI stays live even if a Core upsert fails. Persistence failures are still logged with the watcher id, and received-transaction emission remains behind successful persistence.

Validation: just compile, just test, just lint.

The migration/collision and transfer dedup points remain broader draft follow-ups outside this scoped fix.

Resolved in f546f58

[ovitrif]

Set milestone to 2.5.0 for clarity 👍🏻 , thanks for review & checks @piotr-iohk 🙏🏻

[ovitrif]

Trezor shows 0 balance + empty activity list

Transfer shows duplicate rows - Transfer + Sent

Scope ahead of 2.4.0

The branch is now rebased on the merged #1062 and latest master, and consumes bitkit-core 0.4.0. The old pre-release database state from this report is no longer the branch/base under review. Wallet-scoped persistence is the source of truth, and watcher state is published only after the matching activities and transaction details are available for list/detail navigation.

I reran the full Bridge flow on the current head with two independently funded and mined hardware receives. Both appeared once with the correct wallet scope, and list tabs, tags, tag filtering, Activity Detail, and Explore all used the persisted entries.

Transfer-to-spending now reconciles the watcher-created sent activity with the transfer metadata. The Bridge run showed one pending Transfer / From Savings row, then the same row confirmed after mining while Spending increased by the transferred amount. Device removal purged that wallet's activities, and re-pairing rebuilt its confirmed history.

This work remains scoped to 2.5.0 / #1029. just compile, just test, and just lint all pass on the current head.

Resolved in 5ae816a