Add retry count tracking with exponential backoff

[Copilot]

Jobs now track retry attempts in memory and implement exponential backoff with capped delays. Notifications display retry numbers for visibility into failure patterns.

Changes

• Type system: Added retryCount?: number to JobArgs to persist retry state across job lifecycle
• Retry logic: Modified delayJob() to increment retry count and calculate delay as min(2^(n-1), 60) minutes
• Observability: Notifications and logs now include retry number (e.g., "Retry Fix(webhook): Corrects webhook job execution #3")

Behavior

Retry delays follow: 1min → 2min → 4min → 8min → 16min → 32min → 60min (capped)

const retryCount = (job.data.retryCount || 0) + 1
const delayMinutes = Math.min(Math.pow(2, retryCount - 1), 60)
const message = `Delaying job **${job.data.job}** until ${delayed.toISOTime()} - **Retry #${retryCount}**`
await job.updateData({ ...job.data, delayedMessageId, retryCount })

Cap at 60 minutes prevents unbounded delays for persistent failures (retry #20 would otherwise delay ~1 year).

Original prompt

when retrying, keep in memory the retry number, display it in the notification, and increase the retry delay according to the retry number

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.