[9.0] (backport #10131) Update journald tests now that Filebeat supports watching folders

[mergify]

What does this PR do?

It updates the Journald tests so they're use a folder instead of a glob pattern, which fixes some errors that started appearing after elastic/beats#46682 was merged.

It also updates the Beats dependency version so it includes the fix mentioned above.

Why is it important?

CI was constantly failing, some examples:

• [main][Automation] Update versions #10092
• [8.18][Automation] Update versions #10122
• [9.1][Automation] Update elastic/beats to 10761ca04444 #10094

Checklist

• I have read and understood the pull request guidelines of this project.
• 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/fragments using the changelog tool
• I have added an integration test or an E2E test

## Disruptive User Impact

How to test this PR locally

DEV=true SNAPSHOT=true EXTERNAL=true PACKAGES="docker" DOCKER_VARIANTS="basic,complete,elastic-otel-collector" PLATFORMS=linux/amd64 mage -v package
SNAPSHOT=true INSTANCE_PROVISIONER=kind mage -v integration:testKubernetesSingle TestKubernetesJournaldInputOtel
SNAPSHOT=true INSTANCE_PROVISIONER=kind mage -v integration:testKubernetesSingle TestKubernetesJournaldInput

## Related issues

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

---

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

[mergify]

Cherry-pick of 5f0f2fd has failed:

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

You are currently cherry-picking commit 5f0f2fd3b.
  (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/rm <file>..." as appropriate to mark resolution)
	both modified:   .package-version
	deleted by us:   NOTICE-fips.txt
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum
	deleted by us:   internal/pkg/otel/translate/otelconfig_test.go
	deleted by us:   testing/integration/k8s/testdata/journald-input.yml
	deleted by us:   testing/integration/k8s/testdata/journald-otel.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

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[elasticmachine]

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

[belimawr]

Closing this as 9.0 does not have the test it is fixing.

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: ec33566

Failed CI Steps

• Packaging: linux/amd64 rpm
• Packaging: linux/amd64 rpm
• Packaging: linux/arm64 tar.gz
• Packaging: linux/arm64 tar.gz
• Packaging: windows/amd64 zip
• Packaging: windows/amd64 zip
• Packaging: Containers linux/amd64
• Packaging: Containers linux/arm64

History

• 💔 Build #27625 failed 75e63e0

cc @belimawr

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube