Resolve "Service ping integration with batched background migrations"

What does this MR do and why?

In this merge request, we are tracking via service ping the elapsed time of each batched background migration present in the self-host customer machine. To reduce the payload, we are only collecting finished batched background migrations. We are using a time frame of 7 days.

Output example:

[
  {
    job_class_name: batched_background_migration_a,
    elapsed_time: 3600
  }
]

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #412707 (closed)