[Discuss] Opt in the Cloud Security Posture integration package for automatic upgrades on Kibana upgrades

[eyalkraft]

Motivation

In order to update our integration package with the newest rules and features without friction to our users, we can opt in our integration package for automatic upgrades.

This option is currently hardcoded in Kibana.

Definition of done

• Understand the auto-upgrade behavior and how it works. Comment with this information.
• Knowing what we've learned, consult @tinnytintin10 @tehilashn @amitkanfer if we should opt in
• Open a PR to Kibana if we've decided to auto-upgrade

Out of scope

• Integration changes

Related tasks/epics

• [Fleet] Update logic for "Keep policies up to date" defaults in 8.0 #119126
• [Change Proposal] Add package_policy_upgrade_strategy field to support Fleet upgrade behavior package-spec#244

Checklist

Please follow the following checklist in the beginning of your work, please comment with a suggested of high level solution. It should include:

• Comment describing high level implementation details
  • Include API and data models
  • Include assumptions being taken
  • Provide backward/forward compatibility when changing data model schemas and key constants
  • Mention relevant individuals with a reason (getting feedback, fyi etc)
• Submit a PR for our technical index that includes breaking changes/ new features

Before closing this ticket

• Commit the technical index PR
• Reference to tech-debts that shall be solved as we move forward

[elasticmachine]

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security Posture)

[eyalkraft]

related to

• https://github.com/elastic/security-team/issues/5022

[kfirpeled]

duplicated issue (#144525)