[main](automation) Update .agent-versions.json

[github-actions]

This file is used for picking agent versions in integration tests. It's content is based on the reponse from https://artifacts-api.elastic.co/v1/versions/

[elasticmachine]

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

[mergify]

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

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[cmacknz]

This isn't released yet so shouldn't be appear in this list. The tool is picking up the 8.12.3 staging build, which is essentially equal to 8.12.3-SNAPSHOT since it is produced once per day and isn't a build candidate.

For 8.13.0 it is picking up the build candidate, we should in the future have a specific test pipeline for testing those as they are generated, but for the purposes of testing PRs we are better off with 8.13.0-SNAPSHOT since it moves faster.

[cmacknz]

Probably we should close this, I think the script is going to keep generating updates we want to ignore until we fix it though.

[rdner]

@cmacknz why can't we keep it open until the version is released?
My idea was to keep these PRs until the versions are released and the build passes.

Alternatively, I can put back the logic of checking whether the version is available on our CDN or not (released) and include only released versions.

[rdner]

Probably we should close this, I think the script is going to keep generating updates we want to ignore until we fix it though.

This would lead to new PRs every day until we merge it. I think we should keep the PR open, so the automation does not create new PRs.

[rdner]

Filed an issue for improvements here #4417

[rdner]

Closing this because #4423 was merged.