[7.17](backport #39239) Update x-pack/heartbeat pipeline to match Jenkins

[mergify]

Proposed commit message

In scope of https://github.com/elastic/ingest-dev/issues/3254 - updated x-pack/heartbeat pipeline to match same steps & commands as in Jenkins.
Jenkins vs. Buildkite comparison: https://gist.github.com/oakrizan/ad3b982cd59e42d25d80f664a194998b
BK builds: https://buildkite.com/elastic/beats-xpack-heartbeat/builds?branch=elastic%3Amergify%2Fbp%2F7.17%2Fpr-39239

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

---

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

[mergify]

Cherry-pick of 4f5b23a has failed:

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

You are currently cherry-picking commit 4f5b23a89f.
  (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 <file>..." to mark resolution)
	both modified:   .buildkite/x-pack/pipeline.xpack.heartbeat.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

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2024-05-07T10:20:39.240+0000

• Duration: 10 min 20 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

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

[dliappis]

/test

[dliappis]

LGTM