Add condition to define stack capability requirements

[jsoriano]

What does this PR do?

Add condition to define stack capability requirements.

Why is it important?

There are some features that may be disabled on some deployments, and there are packages that need these features. We need something to indicate the required features so we can prevent users to try to use these packages on deployments where they are not going to work properly.

Checklist

• I have added test packages to test/packages that prove my change is effective.
• I have added an entry in spec/changelog.yml.

Related issues

• Fixes [Change Proposal] Add new field for dependency on stack capabilities #560.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-07-05T14:11:51.177+0000

• Duration: 13 min 47 sec

Test stats 🧪

Test	Results
Failed	0
Passed	894
Skipped	0
Total	894

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (8/8)	💚
Files	70.968% (22/31)	👍
Classes	74.419% (32/43)	👍
Methods	57.778% (78/135)	👍
Lines	43.72% (731/1672)	👍
Conditionals	100.0% (0/0)	💚

[mrodm]

LGTM
Just a suggestion to avoid duplicated values when defining this new field in a manifest.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 83a5dcb

History

• 💚 Build #35 succeeded b33927d

cc @jsoriano