[8.19] (backport #8035) Add Pipeline to deploy custom agent image for FIPS testing

[mergify]

What does this PR do?

Add a new buildkite pipeline to build a custom agent image and use it in an ECH deployment for testing.

Why is it important?

FIPS integration tests will require a custom agent running in the CFT region.

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

N/A

---

This is an automatic backport of pull request #8035 done by Mergify.

[mergify]

Cherry-pick of 5908ed2 has failed:

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

You are currently cherry-picking commit 5908ed22e.
  (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:
	new file:   .buildkite/bk.integration-fips.pipeline.yml
	modified:   .buildkite/hooks/pre-command
	modified:   .buildkite/integration.pipeline.yml
	modified:   .buildkite/scripts/buildkite-integration-tests.sh
	modified:   .ci/updatecli/updatecli-bump-vm-images.yml
	modified:   .tool-versions
	modified:   magefile.go

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   testing/integration/fleetserver_fips_test.go

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]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[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-8035 upstream/mergify/bp/8.19/pr-8035
git merge upstream/8.19
git push upstream mergify/bp/8.19/pr-8035

[michel-laterman]

I've cherry-picked the backport from #8436 as well

[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-8035 upstream/mergify/bp/8.19/pr-8035
git merge upstream/8.19
git push upstream mergify/bp/8.19/pr-8035

[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

• Buildkite Build
• Commit: cf60cf7

History

• 💔 Build #22166 failed e202025
• 💔 Build #22068 failed 7738141

cc @michel-laterman