[8.14] Update versions in tests to 8.13.2 consistently

[cmacknz]

57b7595 bypasses using a PR and committed directly to 8.14 while only partially updating the set of versions used in tests.

Make the versions what they should be in the metricbeat docker-compose.yml file. I believe that main is still using 8.12.x for these tests, I will bump those versions separately.

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[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

• Duration: 76 min 45 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]

Thanks @cmacknz ! It appears that this docker-compose file is a dependency for the x-pack/metricbeat docker-compose file, but it's not defined in the changesets that trigger CI in Jenkins or Buildkite, and as a result a CI run (if a PR got raised) wouldn't have revealed the original issue.

I've raised https://github.com/elastic/ingest-dev/issues/3218 to fix this, and, for now, triggered #39150 (Buildkite run link) to quickly verify that the x-pack/metricbeat Python module integ tests on 8.14 are successful.