chore: remove agent version pinning in the CI

[pkoutsovasilis]

What does this PR do?

This PR removes the pinned AGENT_VERSION, AGENT_PACKAGE_VERSION, and BEAT_VERSION values from the CI environment and updates the .package-version file to 8.17.10.

It also re-enables the upgrade_broken_package_test.go test that was previously skipped due to reliance on pinned versions, since that constraint is now 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.17.10 release. Now that 8.17.10 DRA 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. This only impacts internal CI setup and test gating. End users are not affected.

How to test this PR locally

Open a draft PR 🙂

Related issues

• N/A

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

History

• 💔 Build #24515 failed c38b04a
• 💔 Build #24453 failed a7c3844
• 💔 Build #24338 failed a7c3844

cc @pkoutsovasilis

[elasticmachine]

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

[pchila]

LGTM

[swiatekm]

LGTM