Add time-bounded contexts to AWS API calls

[girodav]

What does this PR do?

This PR adds a time-limit to each AWS API call that is used in metricbeat

Why is it important?

Two main reasons:

• If we encounter a failure in any API we call, we should fail fast.
• Some non-blocking APIs (e.g GetResourceTags) might not work in specific environments (e.g private subnets) and may delay or block the data collection.

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 [AWS Metrics] Add timeout to AWS API calls integrations#6137

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @girodav? 🙏.
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-05-15T16:48:47.080+0000

• Duration: 77 min 34 sec

Test stats 🧪

Test	Results
Failed	0
Passed	1465
Skipped	110
Total	1575

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

[kaiyan-sheng]

Do we need to backport this fix into any branch?