increase the maximum timeout for x-pack-metricbeat

[sharbuz]

What is the problem this PR solves?

Jenkins->Buildkite pipelines migration

fix the issue https://buildkite.com/elastic/beats-xpack-metricbeat/builds/459#018df478-5ada-4edc-91ef-a844244217da/956-10365
by increasing the maximum timeout for x-pack/metricbeat pipeline

Related issues

https://github.com/elastic/ingest-dev/issues/1693

[botelastic]

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

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 1a0a930

cc @sharbuz

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 1a0a930

cc @sharbuz

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 1a0a930

cc @sharbuz

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 1a0a930

cc @sharbuz

[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: 2024-03-01T07:29:46.560+0000

• Duration: 12 min 25 sec

Test stats 🧪

Test	Results
Failed	0
Passed	3
Skipped	0
Total	3

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

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 1a0a930

cc @sharbuz

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 1a0a930

cc @sharbuz