Added a spec for new cloud_defend integration input

[mitodrummer]

What does this PR do?

Creates the spec for a new executable being added for container drift prevention.

Why is it important?

A new cloud defend integration is being created by the AWP team to allow users to protect their containers.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

TODO

Related issues

• Relates New integration created for "cloud_defend" for containers feature integrations#4680

Logs

[mergify]

This pull request does not have a backport label. Could you fix it @mitodrummer? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[lrishi]

Thanks Karl 🥇
Cc: @norrietaylor @m-sample

[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: 2022-11-29T18:45:09.887+0000

• Duration: 18 min 5 sec

Test stats 🧪

Test	Results
Failed	0
Passed	4617
Skipped	13
Total	4630

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	98.333% (59/60)	👍
Files	69.082% (143/207)	👍
Classes	69.133% (271/392)	👍
Methods	53.8% (814/1513)	👍
Lines	38.994% (8795/22555)	👍 0.009
Conditionals	100.0% (0/0)	💚

[oren-zohar]

I think you also need to add the stream like other beats do here:

elastic-agent/specs/filebeat.spec.yml

Line 34 in 67021cf

- name: aws-s3

[oren-zohar]

I would also suggest following the arguments other beats pass, see here

elastic-agent/specs/filebeat.spec.yml

Line 21 in 67021cf

args: &args

you can ignore "filebeat.config.modules.enabled=false" in your case.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b cloud_defend_spec upstream/cloud_defend_spec
git merge upstream/main
git push upstream cloud_defend_spec