Supporting `conditions` configuration in CSPM/KSPM

[oren-zohar]

Motivation Following a fearture request from @BenB196 https://github.com/elastic/cloudbeat/issues/2128

Definition of done

• [ ] Add the conditions vars into the integration manifest, as seen here, for all of our integrations.
• [ ] Add conditions configuration under advanced options into our integration deployment page

Related tasks/epics

• https://github.com/elastic/cloudbeat/issues/2128

[kubasobon]

@maxcold I have prepared a PR adding condition variable to our integration. However I'd like to understand how it's used and what remains to be done to fulfill the Definition of Done. Would you be so kind and find time to chat with me about it?

[maxcold]

From the cloudbeat side, will providing this variable work out of the box?

From the UX side as we have our custom integration design, I guess we need to involve product and design to find the proper place for such settings. In the default "Add integration" design there is a specific section "Settings" where user can change the settings per input (defined as vars in the manifest). We have a custom design for each var, therefore we will need to design and implement the conditions consistently across the inputs we support