action: checks for auditbeat and x-pack/auditbeat

[v1v]

What does this PR do?

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

What's the check stage?

• make check
• make update
• make check-no-changes
• mage check
• mage update

Why is it important?

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

Errors

librpm-dev is required otherwise:

Error: module/system/package/rpm_linux.go:26:10: fatal error: rpm/rpmlib.h: No such file or directory
   26 | #include <rpm/rpmlib.h>
      |          ^~~~~~~~~~~~~~
compilation terminated.
# github.com/elastic/beats/v7/x-pack/auditbeat/module/system/package
Error: module/system/package/rpm_linux.go:26:10: fatal error: rpm/rpmlib.h: No such file or directory
   26 | #include <rpm/rpmlib.h>
      |          ^~~~~~~~~~~~~~

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

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @v1v? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[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-24T14:46:26.224+0000

• Duration: 43 min 52 sec

Test stats 🧪

Test	Results
Failed	0
Passed	570
Skipped	81
Total	651

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

[efd6]

Query about versions of actions/checkout and actions/setup-go (both have a v3). LGTM if these are as desired.

[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-other-modules upstream/feature/check-actions-other-modules
git merge upstream/main
git push upstream feature/check-actions-other-modules