action: checks for x-pack/dockerlogbeat

[v1v]

What does this PR do?

Use GitHub actions to run the check stage for x-pack/dockerlogbeat

What's the check stage?

• mage check
• mage update

Why is it important?

Faster builds by running linting/checks outside of the main CI Pipeline.

Errors

Further details

The existing checks in Jenkins are replaced with GitHub checks, hence the union of these 2 new Github workflows substitutes each former check. Therefore, the same commands will run for the same scenarios.

Results

Nearly 10 minutes since they build was triggered in Jenkins and still waiting for workers to be assigned, while the new GitHub checks finished relatively much faster

Related issues

Similar to #32711

[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-30T16:26:53.032+0000

• Duration: 27 min 18 sec

Test stats 🧪

Test	Results
Failed	0
Passed	6
Skipped	0
Total	6

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

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b feature/check-actions-dockerlogbeat-modules upstream/feature/check-actions-dockerlogbeat-modules
git merge upstream/main
git push upstream feature/check-actions-dockerlogbeat-modules