E2E Test Selection:
This PR introduces a new Hardware Wallet Provider and Bottom Sheet UI components for managing hardware wallet connections (Ledger, QR hardware wallets). Key observations:

1. All files are NEW - These are entirely new files being added to app/core/HardwareWallet/, not modifications to existing code.

2. Not yet integrated - The HardwareWalletProvider is exported from the index but is NOT yet being used anywhere in the app. The grep search shows no consumers outside the HardwareWallet directory itself.

3. Self-contained module - The changes are isolated within app/core/HardwareWallet/ directory with comprehensive unit tests for all new components.

4. Localization changes are additive - Only new keys added to en.json under hardware_wallet namespace, no existing strings modified.

Since the new code is not yet integrated into the app, most E2E tests would not directly exercise this code. However, I'm selecting SmokeAccounts because:

• Hardware wallets are related to account management (adding QR-based hardware wallet accounts)
• The SmokeAccounts tag covers "adding QR-based hardware wallet accounts" per its description
• This provides a sanity check that the new exports don't break existing account-related functionality

The risk is medium because while the code is in a critical path (app/core/), it's entirely new and isolated code that isn't yet wired into the app's main flows.

Performance Test Selection:
This PR adds new Hardware Wallet Provider and Bottom Sheet UI components that are not yet integrated into the app. Since the new code has no consumers and is not being used in any user flows, there is no performance impact to measure. The changes are purely additive new code that won't affect app startup, rendering, or any existing user flows until they are integrated in a future PR.