[8.17] (backport #7958) Pin VM version for check-ci

[mergify]

What does this PR do?

Pinning versions of VM images in the pipelines

Why is it important?

Required to avoid spontaneous failures caused by regular image update && promotion.

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

Related issues

• Relates: Elastic Agent CI fails after VM images got updated #7959

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

[mergify]

Cherry-pick of 1f77033 has failed:

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

You are currently cherry-picking commit 1f7703312.
  (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:   .buildkite/bk.integration.pipeline.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/pipeline.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

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 777cba5

Failed CI Steps

• Win2022:sudo:fleet-privileged
• x86_64:sudo: fleet-privileged

History

• 💔 Build #20446 failed 662844f

cc @oakrizan