Make ci_runners_stale_machines_cleanup_worker job run more frequently

What does this MR do?

Make ci_runners_stale_machines_cleanup_worker job run more frequently. The current daily limit of 1000 stale records per day does not seem to be sufficient to keep with the pace of growth in .com.

The worker seems to be taking between ~400ms - 2secs per run. Spreading the load out by 24 runs should make each run take less time, in addition to making it capable of deleting up to 24000 records per day, giving us a lot of headroom.

Changelog: changed

Repo	MR
GitLab	gitlab!121254 (merged)
GitLab Charts	gitlab-org/charts/gitlab!3187 (merged)
Omnibus ◀	!6906 (merged)

Related issues

Part of gitlab#412298 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• MR title and description are up to date, accurate, and descriptive.
• MR targeting the appropriate branch.
• Latest Merge Result pipeline is green.
• When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

• The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
• If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
• If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
• If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes.
• Documentation created/updated.
• Tests added.
• Integration tests added to GitLab QA.
• Equivalent MR/issue for the GitLab Chart opened.
• Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.