E2E Test Selection:
This PR is a refactoring of the Hardware Wallet Provider module in app/core/HardwareWallet/. The changes include:

1. Code reorganization: Moving hooks from the root directory into a dedicated hooks/ subdirectory (useHardwareWalletStateManager, useDeviceEventHandlers)

2. New hooks extracted from HardwareWalletProvider.tsx: useAdapterLifecycle, useTransportMonitoring, useDeviceDiscovery, useDeviceConnectionFlow - these break down the large provider into smaller, focused hooks

3. API simplification: Removed getConnectionTips() method from adapters and moved the logic to a helper function getConnectionTipsForWalletType() in helpers.ts

4. Component updates: Removed connectionTips prop from HardwareWalletBottomSheet and ConnectingContent components

The public API (HardwareWalletProvider, useHardwareWallet, isUserCancellation) remains unchanged. This is purely an internal refactoring with no functional changes to hardware wallet behavior.

Selected SmokeAccounts because:

• It's the tag most related to hardware wallet functionality (mentions "adding QR-based hardware wallet accounts")
• The HardwareWallet module is used by LedgerConnect and SelectHardware views which are part of account management flows
• While there don't appear to be dedicated hardware wallet E2E tests, running SmokeAccounts provides coverage for account-related flows that might indirectly use this module

The risk is medium because:

• Changes are in critical app/core/ path
• Multiple files changed but all are internal refactoring
• Unit tests have been updated to reflect the changes
• No changes to external API or user-facing behavior

Performance Test Selection:
This PR is a pure code refactoring of the Hardware Wallet Provider module. The changes reorganize hooks into a dedicated directory and extract logic into smaller focused hooks, but do not change any rendering logic, data loading patterns, or state management in ways that would impact performance. No UI components are modified in ways that affect rendering performance, and no new data fetching or processing logic is introduced. The changes are internal architectural improvements that maintain the same functional behavior.