[7.17] feat(slack): apm-server (backport #13307)

[mergify]

Motivation/summary

No more vault access but GitHub secrets

Need to support thread-timestamp

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 #13307 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 055c3a5 has failed:

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

You are currently cherry-picking commit 055c3a56d.
  (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:
	modified:   .github/workflows/prepare-release/action.yml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   .github/workflows/benchmarks.yml
	both modified:   .github/workflows/run-minor-release.yml
	both modified:   .github/workflows/run-patch-release.yml
	deleted by us:   .github/workflows/smoke-tests-schedule.yml

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

[kruskall]

question: why add this ? We don't run benchmarks for 7.17 so I'm not sure we need this

[v1v]

That's how mergify works when there is an automated backport, and includes the conflict label:

• [7.17] feat(slack): apm-server (backport #13307) #13344 (comment)

In this particular case, .github/workflows/benchmarks.yml was not backported originally in the past, but since it was changes among some other things in #13307, when backporting it does create the file from scratch with the conflict label.

We can delete it or keep it - it won't run for 7.17 at all, schedule only works for the default branch, in this particular case main.

[kruskall]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated