[CI] automate update-beats (backport #5692)

[mergify]

This is an automatic backport of pull request #5692 done by Mergify.
Cherry-pick of bd10c37 has failed:

On branch mergify/bp/7.17/pr-5692
Your branch is up to date with 'origin/7.17'.

You are currently cherry-picking commit bd10c37b.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   .ci/update-beats.groovy
	modified:   .mergify.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both added:      .ci/scripts/update-beats.sh

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[v1v]

Then three required backports after this one:

• update beats: fix new file location #6700
• update beats: avoid failing if no files have changed #6677
• [bump][automation] skip backports for the automation #6247

[apmmachine]

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /hey-apm : Run the hey-apm benchmark.

• /package : Generate and publish the docker images.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)