[Change Proposal] Allow to declare a maturity level in the agentless deployment mode

[jsoriano]

There are cases where the agentless deployment mode of a package has a different maturity level than the default one. In these cases, we would want to be able to define it, so UIs can make informed decisions on the versions of the packages used and how they are presented to users.

The change would be to add a release parameter to the agentless deployment mode, so for example we can have this configuration to indicate that even if the package is GA, the agentless deployment mode is beta:

deployment_modes:
    agentless:
      enabled: true
      release: beta   # <-- new field

This new field is only intended for high-level UIs, and not intended to affect discoverability of packages through the Package Registry.

[theletterf]

Following up for docs automation changes.

[MichelLosier]

Here is what I see as the implementation plan for this:

Package spec

• As proposed, add an optional release field in deployment_modes.agentless
• Seems we have nuanced existing definitions around beta, and preview. I think we should support those values as well to be consistent with package level semver translations of releases. (Kibana descriptions)
• Constraints:
  - only values beta, preview
  - not allowed where agentless is the only deployment method in a single policy_template package. Kind of an edge case for someone to do this, but this would create confusion with the semver evaluation of the release state.

Kibana

• fleet/epm/packages API
  • Update PackageInfo and schema types to support the new optional release field in deployment_modes.agentless
• Integrations list UI
  • Show agentless deployment method release tag in integration tile when:
    • The "Setup method" filter is set to "Agentless", and is a policy_template integration
    • Agentless is the only deployment method
    • Agentless is the default deployment method
• Integration details view
  • Show agentless deployment method release tag in header tag row when:
    • Agentless is the only deployment method
    • Agentless is the default deployment method
• Package policy form
  • Show release method tag next to deployment radio option

Integrations

• Update agentless deployment configs with release field where necessary.

[MichelLosier]

Created implementation issues for Kibana and Integrations:

• [Fleet] Support agentless deployment mode release field kibana#262089
• Add "release" field to agentless deployment modes integrations#18294

[MichelLosier]

An adjustment on approach while discussing with @kpollich :

We'll have the default value for release be beta, and require GA be explicitly declared. This is a safer default to work with, so we are not accidentally flagging an agentless deployment as GA because of absence.

Although we could find ourselves in the future defining other states of less maturity like technical preview, starting with a beta release as default represents the most probable starting state for agentless deployments.