[Cloud Security] [BUG] [CNVM] Cloudformation deployment doesn't appear when not installed to a newly created agent policy

[kfirpeled]

Motivation

In 8.8 when we introduced CNVM and CloudFormation deployment we allowed the user to create a new Agent Policy with CNVM and then let him/her deploy it using CloudFormation.

However, there are some edge cases which CloudFormation deployment won't be available to the user.
The root cause for it is having a variable in the input, that translates to saving these variables to the AgentPolicy instead of the PackagePolicy.

Steps to reproduce:

1. Have an existing agent policy prior to 8.8 / Create an agent policy without CNVM
2. Add CNVM
3. Open agent deployment instructions (Add Agent)

Expected: CloudFormation deployment option is available
Actual: CloudFormation deployment option is missing

Screen.Recording.2023-04-20.at.13.38.54.mov

Definition of done

• Understand how cloudformation data can be saved over the package policy instead of agent policy
• Make sure we are backward compatible with existing Agent Policies from 8.8

Out of scope

Related tasks/epics

• [Cloud Security] [Vulnerability Management] [Add Agent] Add CloudFormation Elastic Agent install method #153067

[elasticmachine]

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

[oren-zohar]

Verified: