[8.19] (backport #8605) [Synthetics] Add e2e test for synthetics deps in complete variants

[mergify]

What does this PR do?

Add tests to check synthetics dependencies for complete variant docker packages. These will prevent the possibility of an unrelated change removing the required dependencies.

Why is it important?

We have seen instances where unrelated changes to the docker template have caused the generated -complete variants to be missing synthetics dependencies.

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

How to test this PR locally

1. Edit elastic-agent docker template sections where synthetics-deps are installed.
2. Build agent locally.
3. Wait for testing step to fail.
4. Restore elastic-agent template.
5. Build and wait for completion.

Related issues

• Relates Elastic Agent Complete - browser monitors cannot be created outside the official elastic docker image #8434.

  ---

  This is an automatic backport of pull request [Synthetics] Add e2e test for synthetics deps in complete variants #8605 done by Mergify.

[mergify]

Cherry-pick of f8c1f2e has failed:

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

You are currently cherry-picking commit f8c1f2ef0.
  (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:   dev-tools/packaging/testing/package_test.go

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]

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

[elasticmachine]

Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)

[pchila]

@emilioalvap as author of the original PR #8605, could you please fix the backports ?

Thank you

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: ce9b6bc

Failed CI Steps

• fips:x86_64:sudo-false:fleet
• fips:arm64:sudo-false:fleet

History

• 💔 Build #23220 failed 0c369a3
• 💔 Build #23076 failed 567a93e

cc @emilioalvap

[mergify]

This pull request has not been merged yet. Could you please review and merge it @emilioalvap? 🙏

[emilioalvap]

@pchila Thanks for the reminder. This should be fixed now, please review.