Fixes #4535

Problem

The backupDSLoop encounters 'driver: bad connection' errors when trying to mark the end of backup operations. This happens when the database connection is lost during long-running migration operations.

Solution

• Add isRetryableError() function to detect retryable connection errors
• Add retryWithBackoff() function with exponential backoff (1s, 2s, 4s, max 30s)
• Wrap journalMarkDoneInTx with retry logic (up to 3 retries)

Changes

• Added helper functions for retryable error detection
• Applied retry logic to journal marking operations in migration

…y logic (rudderlabs#4535)

…od (rudderlabs#6630)

…event context deadline errors (rudderlabs#6349)

This PR is considered to be stale. It has been open 20 days with no further activity thus it is going to be closed in 7 days. To avoid such a case please consider removing the stale label manually or add a comment to the PR.