chore: remove agent version pinning in the CI

[pkoutsovasilis]

What does this PR do?

This PR removes the manual version pinning for AGENT_VERSION, AGENT_PACKAGE_VERSION, and BEAT_VERSION from our CI configuration files, and bumps the .package-version file to 8.18.5.

It also re-enables a test that was previously skipped due to the version pinning, as the condition blocking its execution has now been resolved.

PS: as discussed here a review from observablt-ci and observablt-ci-contractors is not required (cc @ebeahan @pierrehilbert )

Why is it important?

The version pinning was introduced as a temporary workaround to support the 8.18.4 release. Now that 8.18.5 is released, we are reverting to an unpinned state

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 expected. This change only affects CI configuration and test gating logic.

How to test this PR locally

Open a draft PR 🙂

Related issues

• N/A

[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 ci/818_revert_agent_pinning upstream/ci/818_revert_agent_pinning
git merge upstream/8.18
git push upstream ci/818_revert_agent_pinning

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 5864ac8

Failed CI Steps

• Win2022:sudo:fleet
• Win2022:sudo:fleet
• Win2022:sudo:fleet-privileged
• Win2022:sudo:fleet-privileged
• Win2022:sudo:upgrade
• Win2022:sudo:upgrade
• Win2025:sudo:fleet
• Win2025:sudo:fleet
• Win2025:sudo:fleet-privileged
• Win2025:sudo:fleet-privileged
• Win2025:sudo:upgrade
• Win2025:sudo:upgrade
• x86_64:sudo: upgrade
• x86_64:sudo: fleet
• x86_64:sudo: fleet-airgapped
• x86_64:sudo: fleet-airgapped
• x86_64:sudo: fleet-airgapped-privileged
• x86_64:sudo: fleet-airgapped-privileged
• x86_64:sudo: fleet-privileged
• x86_64:sudo: fleet-privileged
• arm:sudo: upgrade
• arm:sudo: fleet
• arm:sudo: fleet
• x86_64:sudo: upgrade
• x86_64:sudo: fleet
• x86_64:sudo: fleet
• x86_64:sudo: fleet-airgapped
• x86_64:sudo: fleet-airgapped
• x86_64:sudo: fleet-airgapped-privileged
• x86_64:sudo: fleet-airgapped-privileged
• x86_64:sudo: fleet-privileged
• x86_64:sudo: fleet-privileged

History

• 💔 Build #24342 failed dae34f9

cc @pkoutsovasilis

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

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

[pchila]

LGTM