[7.17](backport #32746) action: checks for filebeat and x-pack/filebeat

[mergify]

This is an automatic backport of pull request #32746 done by Mergify.
Cherry-pick of da20ec7 has failed:

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

You are currently cherry-picking commit da20ec779b.
  (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)

Changes to be committed:
	new file:   .github/workflows/check-filebeat.yml
	new file:   .github/workflows/check-xpack-filebeat.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/workflows/opentelemetry.yml
	both modified:   filebeat/Jenkinsfile.yml
	both modified:   x-pack/filebeat/Jenkinsfile.yml

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

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[botelastic]

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

[elasticmachine]

💔 Build Failed

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: 2022-08-25T08:39:09.819+0000

• Duration: 7 min 17 sec

Steps errors

Expand to view the steps failures

Read yaml from files in the workspace or text.

• Took 0 min 0 sec . View more details here
• Description: filebeat/Jenkinsfile.yml

Error signal

• Took 0 min 0 sec . View more details here
• Description: Error 'while scanning a simple key in 'reader', line 16, column 1: <<<<<<< HEAD ^could not find expected ':' in 'reader', line 17, column 9: lint: ^'

❕ Flaky test report

No test was executed to be analysed.

🤖 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 Failed

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: 2022-08-25T09:35:11.805+0000

• Duration: 2 min 8 sec

Steps errors

Expand to view the steps failures

Git fetch

• Took 0 min 2 sec . View more details here
• Description: git fetch https://${GIT_USERNAME}:${GIT_PASSWORD}@github.com/elastic/beats.git +refs/pull/*/head:refs/remotes/origin/pr/* > fetch.log 2>&1

Archive the artifacts

• Took 0 min 1 sec . View more details here
• Description: fetch.log

❕ Flaky test report

No test was executed to be analysed.

🤖 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

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: 2022-08-25T09:00:05.368+0000

• Duration: 132 min 39 sec

Test stats 🧪

Test	Results
Failed	0
Passed	9196
Skipped	839
Total	10035

💚 Flaky test report

Tests succeeded.

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