[8.19] (backport #10906) fix(bk): serverless-beats-tests start failing after merging #10734

[mergify]

What does this PR do?

Restore the previous environmental context for the serverless-beats-tests
Run serverless-beats-tests if touching some of the core files.

Why is it important?

Regression, and help with early detection

Checklist

• I have read and understood the pull request guidelines of this project.
• 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/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

NA

Only in the CI

This PR triggered:

• https://buildkite.com/elastic/beats-agent-serverless-tests/builds/1293

Related issues

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

---

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

[mergify]

Cherry-pick of 0a1cf18 has failed:

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

You are currently cherry-picking commit 0a1cf18cf.
  (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/hooks/pre-command
	both modified:   .buildkite/pipeline.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 is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.19/pr-10906 upstream/mergify/bp/8.19/pr-10906
git merge upstream/8.19
git push upstream mergify/bp/8.19/pr-10906

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 224974b

Failed CI Steps

• Win2025:sudo:default
• Win2025:sudo:default
• x86_64:sudo: default

History

• 💔 Build #29662 failed d2b7925
• 💔 Build #29658 failed 087390b

cc @v1v