fix(e2e): keep lite mainnet cron loop running on failures

[Ansonhkg]

WHAT

Log and swallow errors in the lite mainnet uptime cron runner so failures don’t terminate the loop, allowing continued health checks.

#Example Usage:

// BEFORE
await runLiteMainnetOnce(runWithStatus); // throws -> Jest exits

// AFTER
try {
  await runLiteMainnetOnce(runWithStatus);
} catch (error) {
  console.error('[lite-mainnet-uptime] Run encountered an error', error);
}

[Copilot]

Pull request overview

This PR fixes the lite mainnet uptime cron runner to handle failures gracefully without terminating the monitoring loop. Previously, uncaught errors would cause Jest to exit, stopping all subsequent health checks.

Key changes:

• Added try-catch error handling in the runWithStatus wrapper to log and swallow individual test failures
• Added try-catch error handling around runLiteMainnetOnce to catch initialization and orchestration errors

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.