[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: ```json
{
"version": "9.2.0-SNAPSHOT",
"build_id": "9.2.0-b1f0338e",
"manifest_url": "https://snapshots.elastic.co/9.2.0-b1f0338e/manifest-9.2.0-SNAPSHOT.json",
"summary_url": "https://snapshots.elastic.co/9.2.0-b1f0338e/summary-9.2.0-SNAPSHOT.html",
"core_version": "9.2.0",
"stack_build_id": "9.2.0-b1f0338e-SNAPSHOT"
}

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

[elasticmachine]

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

[elasticmachine]

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

[pkoutsovasilis]

@ycombinator based on our previous discussion here I removed Testing:run:TestUpgradeIntegrationsServer label

[pchila]

Update looks good and consistent with the current DRA info for main

{
  "version" : "9.2.0-SNAPSHOT",
  "build_id" : "9.2.0-b1f0338e",
  "manifest_url" : "https://snapshots.elastic.co/9.2.0-b1f0338e/manifest-9.2.0-SNAPSHOT.json",
  "summary_url" : "https://snapshots.elastic.co/9.2.0-b1f0338e/summary-9.2.0-SNAPSHOT.html"
}

Waiting for CI to complete successfully before approving

[pkoutsovasilis]

Thanks for the extra check @pchila much appreciated. Echoing the same message I see that this PR behaves as expected

1. Uses the latest snapshot DRA for main branch as of now

{
  "version" : "9.2.0-SNAPSHOT",
  "build_id" : "9.2.0-b1f0338e",
  "manifest_url" : "https://snapshots.elastic.co/9.2.0-b1f0338e/manifest-9.2.0-SNAPSHOT.json",
  "summary_url" : "https://snapshots.elastic.co/9.2.0-b1f0338e/summary-9.2.0-SNAPSHOT.html"
}

2. We do build from this DRA https://buildkite.com/elastic/elastic-agent/builds/24885#019883d6-39fd-4b41-9f09-3b38dc14190a/157-159
3. ESS stacks components are created from this build-id

• non-FIPS https://buildkite.com/elastic/elastic-agent/builds/24885#019883f7-28e6-4931-b7b8-023f93ccfa98/161-245
• FIPS https://buildkite.com/elastic/elastic-agent/builds/24885#019883f7-2794-4b67-91af-b0b669c10d6c/162-206
• Custom ECH server https://buildkite.com/elastic/elastic-agent/builds/24885#019883f7-28e5-420b-9d56-c205270c3f8a/215-299

PS: there are some PR description formatting issue though

[pkoutsovasilis]

@ebeahan @pierrehilbert this fails because fips:upgrade-ech-deployment which is a known problem. I was expecting the removal of the label to skip this test but it doesn't. That said, could we force merge this as it updates our CI to the latest available snapshot DRA?

[pchila]

Error in CI FIPS tests is likely due to the recent issues with 8.19.0 and 9.1.0 versions.
Everything else is green.

LGTM

[ebeahan]

Force merging by request from @pkoutsovasilis to update to the latest snapshot DRA. Holding off to try rebuilding once more first.

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

• Buildkite Build
• Commit: f4b99a3

Failed CI Steps

• fips:upgrade-ech-deployment
• fips:upgrade-ech-deployment

History

• 💔 Build #24885 failed f4b99a3

cc @pkoutsovasilis

[pkoutsovasilis]

@ebeahan the rebuild effort without the label didn't cause the fips:upgrade-ech-deployment go away, so you know

[ycombinator]

@ebeahan the rebuild effort without the label didn't cause the fips:upgrade-ech-deployment go away, so you know

Thanks for trying to rebuild, @pkoutsovasilis, and ++ to @ebeahan force merging this PR at this point.

Meanwhile, I've created #9286 to address the CI bug with removing the label.