Requeue BackfillJiraTrackerDataShardingKey migration

What does this MR do and why?

This MR requeues jira_tracker_data sharding key backfill. It has been observed that there are 84 leftover records to be updated after the migration has been finished. We have added a db trigger to jira_tracker_data so that sharding key is always set on insert so we should be in a good position to reenqueue this batched background migration to fix the leftover records.

References

#545940 (closed)

Screenshots or screen recordings

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.