[awss3][automation] Fix skipping aws tests in automation

[bhapas]

What does this PR do?

This PR fixes the Integration test CI job to run the awss3 input_integration_test on AWS resources which were getting skipped all the time.

Current Behaviour

[2023-07-13T21:20:45.448Z] === Skipped
[2023-07-13T21:20:45.448Z] 
[2023-07-13T21:20:45.448Z] === SKIP: x-pack/filebeat/input/awss3 TestInputRunSQS (0.00s)
[2023-07-13T21:20:45.448Z]     input_integration_test.go:151: Run 'terraform apply' in _meta/terraform to setup S3 and SQS for the test.
[2023-07-13T21:20:45.448Z] 
[2023-07-13T21:20:45.448Z] === SKIP: x-pack/filebeat/input/awss3 TestInputRunS3 (0.00s)
[2023-07-13T21:20:45.448Z]     input_integration_test.go:202: Run 'terraform apply' in _meta/terraform to setup S3 and SQS for the test.
[2023-07-13T21:20:45.448Z] 
[2023-07-13T21:20:45.448Z] === SKIP: x-pack/filebeat/input/awss3 TestGetRegionForBucketARN (0.00s)
[2023-07-13T21:20:45.448Z]     input_integration_test.go:325: Run 'terraform apply' in _meta/terraform to setup S3 and SQS for the test.
[2023-07-13T21:20:45.448Z] 
[2023-07-13T21:20:45.448Z] === SKIP: x-pack/filebeat/input/awss3 TestPaginatorListPrefix (0.00s)
[2023-07-13T21:20:45.448Z]     input_integration_test.go:343: Run 'terraform apply' in _meta/terraform to setup S3 and SQS for the test.
[2023-07-13T21:20:45.448Z] 
[2023-07-13T21:20:45.448Z] === SKIP: x-pack/filebeat/input/awss3 TestInputRunSNS (0.00s)
[2023-07-13T21:20:45.448Z]     input_integration_test.go:391: Run 'terraform apply' in _meta/terraform to setup S3 and SQS for the test.

PR Fix

[2023-07-15T07:12:41.318Z] **ok**  	github.com/elastic/beats/v7/x-pack/filebeat/input/awss3	161.899s	coverage: 79.7% of statements

Full Log here - https://beats-ci.elastic.co/job/Beats/job/beats/job/PR-36054/27/consoleText

Additional issues found

While fixing the skipped tests issue, it has been observed that the input metrics added to the test were failing for both SQS and SNS tests and the test code has been commented out here

This is outside the scope of the PR and shall be looked at in separate issue - #36077

Why is it important?

The awss3 input integration tests were never run and a false positive result is being returned on CI

-->

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

Related issues

• Relates #34003

[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-17T08:12:30.991+0000

• Duration: 145 min 28 sec

Test stats 🧪

Test	Results
Failed	0
Passed	30570
Skipped	2208
Total	32778

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

[bhapas]

/test

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)