Fixes and Performance Improvements

[xavier-brochard]

Fix WebSocket Connection Reliability & Optimize Background Tasks

This PR addresses three key issues: WebSocket connection reliability, resource optimization for background tasks, and proper handling of native assets in asset list updates.

🔌 WebSocket Connection Reliability

Problem: WebSocket connections can be silently dropped after extended periods of inactivity (e.g., over weekends) without triggering close events that our reconnection logic relies on. This leaves the application without active connections when they're needed.

Solution:

• Added onActive lifecycle handler: Ensures WebSocket connections are properly established whenever the snap becomes active

Changes:

• Added onActive and onInactive lifecycle event handlers in src/index.ts
• Updated WebSocketConnectionService to handle the onActive event alongside existing onStart, onUpdate, and onInstall events

⚡ Convert Cronjobs to Self-Scheduling Background Events

Problem: The refresh cronjobs for Send flow and confirmation estimation were running every X seconds regardless of whether the interfaces were open, wasting resources when the functionality wasn't needed.

Solution: Convert periodic cronjobs to self-scheduling background events that:

• Only run when the relevant interface is actually open
• Schedule their next execution conditionally
• Automatically stop when interfaces are closed

Changes:

• Moved refreshSend and refreshConfirmationEstimation from /cronjobs/ to /backgroundEvents/
• Updated scheduling logic to be self-managing
• Removed unnecessary cronjob entries from snap.manifest.json
• Background events now schedule themselves only when interfaces are active

🪙 Fix Native Asset Removal Logic

Problem: Native assets (SOL) were being incorrectly removed from the account asset list when they had zero balance, which should never happen as native assets should always be visible.

Solution:

• Added logic to prevent native assets from being included in the removed array of KeyringEvent.AccountAssetListUpdated
• Native assets are now always preserved in the asset list regardless of balance

Changes:

• Added isNativeAsset() helper function in AssetsService
• Updated asset removal logic to exclude native assets
• Added comprehensive unit test to ensure native assets are never removed

This ensures reliable WebSocket connectivity, optimizes resource usage, and maintains proper asset list behavior across all scenarios.

[orestiseth]

Q: This will run every 20 seconds or it will run just once? In the case of being periodic will it get cancelled when the confirmation interfaced gets closed?

[xavier-brochard]

This only schedules the next run.
Incidentally, if the confirmation interface gets closed, it runs, but doesn't schedule an other run.

It's basically a loop system, where we enter the loop when the confirmation interface renders, and exit the loop when the interface get closed.