feat: add alert for unfinalized burn events

[ashwinrava]

Adds error logging when CCTP burn events that were published to the finalizer haven't been finalized on the destination chain within the expected timeframe.

Changes

• Added checkForUnfinalizedBurnEvents() method to CctpFinalizerService
• Queries for CctpFinalizerJob records older than 30 minutes but younger than 24 hours (so we don't infinitely log for old/expired/unnecessary unprocessed records)
• Checks if corresponding MessageReceived exists on destination chain (matched by sourceDomain + nonce)
• Logs error with notificationPath: "across-indexer-error" if no mint found (triggers Slack/PagerDuty alert)

Testing

Ran indexer locally and set up DB for a completed and pending job:

2026-01-05 19:37:24 [�[34mdebug�[39m]: {
  "at": "CctpFinalizerService#checkForUnfinalizedBurnEvents",
  "message": "Burn event has been finalized",
  "sourceChainId": "137",
  "destinationChainId": 8453,
  "burnTransactionHash": "0xcaf5a690c6267a00c96f7e700ad0e28fecc69f5dc5c02b78f7a9d4f543c696c3",
  "bot-identifier": "NO_BOT_ID",
  "run-identifier": "b45b4ab8-a7fe-46dc-921f-2f8981b3c648"
}

2026-01-05 19:37:24 [�[31merror�[39m]: {
  "at": "CctpFinalizerService#checkForUnfinalizedBurnEvents",
  "message": "CCTP burn event has not been finalized after 67207 minutes",
  "notificationPath": "across-indexer-error",
  "sourceChainId": "137",
  "destinationChainId": 42161,
  "burnTransactionHash": "0xa33f31ede12c361b97b2b4e8f5b525190e67efae5e3d54ec3aa87baef811a36e",
  "burnBlockNumber": 77454018,
  "amount": "1000000",
  "depositor": "0x9A8f92a830A5cB89a3816e3D267CB7791c16b04D",
  "mintRecipient": "0x9A8f92a830A5cB89a3816e3D267CB7791c16b04D",
  "sourceDomain": 7,
  "nonce": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "jobCreatedAt": "2025-11-20T03:30:17.294Z",
  "elapsedMinutes": 67207,
  "bot-identifier": "NO_BOT_ID",
  "run-identifier": "b45b4ab8-a7fe-46dc-921f-2f8981b3c648"
}

[melisaguevara]

looks good. Just one nit.

[amateima]

Is there a reason this isn't in a separate service? It feels conceptually different from the finalization publishing logic. Could be cleaner as its own monitoring service

[amateima]

nit: for increased readability I'd format this to smth like

• "now() - job.createdAt > interval '30 minutes'"
• "now() - job.createdAt < interval '24 hours'"

[ashwinrava]

Addressed in 25ae6f8.