[functionbeat] Fix deployment for CloudWatch Logs function type

[gemabarni]

Proposed commit message

AWS CloudFormation started validating CloudWatch's permission to invoke a Lambda function when deploying a subscription filter, which could result in Functionbeat deployment errors: #33173. Although no AWS documentation states this explicitly, all of their official guides imply that the permission should always be created first. Examples:

• https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/SubscriptionFilters.html#LambdaFunctionExample
• https://repost.aws/knowledge-center/lambda-cloudwatch-filter

This PR introduces a dependency between the two entities to make sure that the permission is already present when the subscription filter gets deployed.

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.

Related issues

• Closes functionbeat - Could not execute the lambda function #33173

[botelastic]

This pull request doesn't have a Team:<team> label.

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @gemabarni? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

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

[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-08-14T08:49:17.566+0000

• Duration: 48 min 10 sec

Test stats 🧪

Test	Results
Failed	0
Passed	489
Skipped	6
Total	495

💚 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 and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

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

[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 fix-logs-deploy upstream/fix-logs-deploy
git merge upstream/main
git push upstream fix-logs-deploy

[jonathan-franzen]

When will this get merged? I have major issues with my deployment

[dgsamper]

Our deploy was impacted by this too. We actually had to deploy with just one log group, and add the others manually, to be able to work. Any plans on merging this PR or no more support for functionbeat?

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @gemabarni? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

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