[Fleet] Fix release fallback logic in Fleet package archive code

[kpollich]

Summary

Ref elastic/package-spec#225
Ref elastic/package-registry#785
Ref #133270

Adds fallback logic based on the version value in an integration's manifest.yml to populate the release field when it is excluded from the manifest.yml file. Generation of the release value is based on whether the integration's release is a prerelease (per semver spec) or its major version is less than 1. See package spec issues and package registry PR referenced above for further context.

This should unblock #133270, which is failing because the latest APM package no longer includes a release value in its manifest.yml as of elastic/apm-server#7792.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[nchaulet]

🚀 Is APM the only package impacted by this?

[kpollich]

🚀 Is APM the only package impacted by this?

I ran the generatePackageInfoFromArchiveBuffer against the latest version of all other bundled packages and it seems APM is the only one where release has been formally removed from its manifest. So yes APM should be the only package affected so far.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 5de9f27
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

✅ unchanged

History

• 💔 Build #49396 failed 3167cf5
• 💔 Build #49387 failed 74f35c9
• 💔 Build #49370 failed 6ad7603
• 💔 Build #49367 failed 6b02225
• 💔 Build #49354 failed dc553aa

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @kpollich

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation