[8.19](backport #49529) Fix the globs for collecting artifacts from failed tests

[mergify]

Proposed commit message

Ensure everything on the following folders are always collected by
BuildKite after the tests.
 - filebeat/build/input-test
 - filebeat/build/integration-tests
 - x-pack/filebeat/build/input-test
 - x-pack/filebeat/build/integration-tests

Those folders contain the state of failed tests, which is very helpful
to investigate failing and flaky tests.

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. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
• I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

---

This is an automatic backport of pull request #49529 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 8b5e28d has failed:

On branch mergify/bp/8.19/pr-49529
Your branch is up to date with 'origin/8.19'.

You are currently cherry-picking commit 8b5e28d49.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .buildkite/filebeat/filebeat-pipeline.yml
	both modified:   .buildkite/x-pack/pipeline.xpack.filebeat.yml

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[github-actions]

🤖 GitHub comments

Just comment with:

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

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[mallendem]

PR Owner: For some reason this change wasn't backported to this branch