Improve retry and failure handling for failed overage submission batches

Problem

When an overage submission batch fails, we currently have to manually update the batch status or delete and rerun submission. This is error-prone and inefficient.

Current State

• Failed batch requires manual status update or deletion
• Rerun submission process is manual
• No automated retry mechanism
• Difficult to track failed batches

Acceptance Criteria

• Implement automated retry mechanism for failed batches
• Add exponential backoff for retries
• Improve failure tracking and visibility
• Create dashboard for failed batch monitoring
• Implement automatic recovery where possible
• Document failure handling process