[FIPS] Only consider versions available in ECH region for TestUpgradeIntegrationsServer

[ycombinator]

What does this PR do?

This PR restricts the versions used as start versions in TestUpgradeIntegrationsServer to those actually available in the ECH region where the integrations server is being run.

Why is it important?

The test should not attempt to use a start version that doesn't actually exist in the ECH region where the integrations server deployment will be created.

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

None; this PR modifies an integration test.

Related issues

Follow up to #9207 (comment)

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?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @ycombinator? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[ycombinator]

CI is green while running the TestUpgradeIntegrationsServer test but without including the version change in #9172. I will now include that change in this PR — by rebasing on main since #9172 has now been merged — as a test to see if the 8.19.0 version gets excluded as expected and CI still remains green.

[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 it-fips-upgrade-integrations-server-versions upstream/it-fips-upgrade-integrations-server-versions
git merge upstream/main
git push upstream it-fips-upgrade-integrations-server-versions

[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]

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

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 3a42695

History

• 💔 Build #24905 failed 3820a0b
• 💔 Build #24865 failed d4ae061
• 💔 Build #24855 failed de1f3a4

cc @ycombinator

[pkoutsovasilis]

I can see that the issue we faced on the PR on main is no longer here and the code checks out, thus, LGTM