Background migration for setting Jira tracker data deployment type

What does this MR do?

This is a reimplementation of !37002 (merged), using batching rather than individual jobs

Background Migration Details

• Table: jira_tracker_data
• Rows: ~84000
• Targeted rows: ~75000
• Delay between jobs: 2.minutes
• Batch size: 1000
• Estimated number of jobs: 75000 / 1000 = 75
• Estimated execution time for all jobs: 75 * 2.minutes / 60 ~= 2.5 hours

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #243607 (closed)