Skip flaky Filebeat cloudAWS tests

[belimawr]

Proposed commit message

Skip the failing tests until a fix is found.

## Checklist
## Author's Checklist
## How to test this PR locally
## Related issues

• Closes: Build 1883 for main with status FAILURE #36548
• Relates: x-pack/metricbeat-cloudAWS goIntegTest is consistently failing #36425

## Use cases
## Screenshots
## Logs

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @belimawr? 🙏.
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-09-11T17:00:04.742+0000

• Duration: 76 min 55 sec

Test stats 🧪

Test	Results
Failed	0
Passed	3177
Skipped	174
Total	3351

💚 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!)

[cmacknz]

Backport this if it is also failing in the other branches.

[belimawr]

Backport this if it is also failing in the other branches.

Thanks!

At the moment I don't recall it failing in any other branch. I'll keep that in mind.