[8.x](backport #16605) deps(gh-actions): use main for the elastic gh actions

[mergify]

Motivation/summary

We trust the elastic GH actions, and that can help us to ship new features faster

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

Related issues

---

This is an automatic backport of pull request #16605 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 9d8df85 has failed:

On branch mergify/bp/8.x/pr-16605
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit 9d8df853.
  (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)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   .github/workflows/docs-build.yml
	deleted by us:   .github/workflows/docs-cleanup.yml

no changes added to commit (use "git add" and/or "git commit -a")

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

[mergify]

This pull request has not been merged yet. Could you please review and merge it @v1v? 🙏

[mergify]

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #16609 has been dequeued, merge conditions unmatch:

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
• check-success=lint
• check-success=system-test
• check-success=test (macos-latest)
• check-success=test (windows-latest)
• any of [🛡 GitHub branch protection]:
  • check-neutral = lint
  • check-skipped = lint
  • check-success = lint
• any of [🛡 GitHub branch protection]:
  • check-neutral = buildkite/docs-build-pr
  • check-skipped = buildkite/docs-build-pr
  • check-success = buildkite/docs-build-pr
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
• check-success=CLA
• any of [🛡 GitHub branch protection]:
  • check-success = CLA
  • check-neutral = CLA
  • check-skipped = CLA

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.