[main][Automation] Update versions

[github-actions]

These files are used for picking the starting (pre-upgrade) or ending (post-upgrade) agent versions in upgrade integration tests.

The content is based on responses from https://www.elastic.co/api/product_versions and https://snapshots.elastic.co

The current update is generated based on the following requirements:

Package version: 9.2.0

{
  "UpgradeToVersion": "9.2.0",
  "CurrentMajors": 1,
  "PreviousMajors": 1,
  "PreviousMinors": 2,
  "SnapshotBranches": [
    "9.1",
    "9.0",
    "7.17"
  ]
}

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

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

[pkoutsovasilis]

ok everything is correct here except this one 🤔

[pkoutsovasilis]

Ok I just realised that this is correct indeed, according to the code this is what we are after

elastic-agent/magefile.go

Lines 2422 to 2435 in 0340e6b

	maxSnapshots := 3
	branches, err := git.GetReleaseBranches(ctx)
	if err != nil {
	return fmt.Errorf("failed to list release branches: %w", err)
	}
	// -1 because we manually add 7.17 below
	if len(branches) > maxSnapshots-1 {
	branches = branches[:maxSnapshots-1]
	}
	// it's not a part of this repository, cannot be retrieved with `GetReleaseBranches`
	branches = append(branches, "7.17")

[pierrehilbert]

We may need to do an exception for 8.19 in the same way we are doing for 7.17 as it will last for a long time.
WDYT?

[pkoutsovasilis]

okay that makes sense, let's keep this PR at bay then, and I am gonna open a PR with the 8.19 expection just for the 9.x branches 🙂

[pkoutsovasilis]

@ycombinator also in this PR TestUpgradeIntegrationsServer runs nothing 🙁

[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: c9e3382

[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 update/main-update-agent-versions-15991470246 upstream/update/main-update-agent-versions-15991470246
git merge upstream/main
git push upstream update/main-update-agent-versions-15991470246

[pkoutsovasilis]

closing as this one #8761 got merged in main