action: run check, check-default and pre-commit

[v1v]

What does this PR do?

Use GitHub actions to run the check stage default commands for:

• only docs
• everytime
• pre-commit

On a PR basis

Why is it important?

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

Issue

Similar to #32711

Failures

libsystemd-dev is required otherwise

Error: ../../../../go/pkg/mod/github.com/coreos/go-systemd/v22@v22.3.2/sdjournal/journal.go:27:11: fatal error: systemd/sd-journal.h: No such file or directory
   27 | // #include <systemd/sd-journal.h>
      |           ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Error: failed running go vet, please fix the issues reported: running "go vet ./..." failed with exit code 2

librpmlib-dev is required otherwise

# 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>
      |          ^~~~~~~~~~~~~~
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>
      |          ^~~~~~~~~~~~~~
compilation terminated.
Error: failed running go vet, please fix the issues reported: running "go vet ./..." failed with exit code 2
make[1]: *** [../../dev-tools/make/mage.mk:21: check] Error 1

[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-18T11:05:46.720+0000

• Duration: 87 min 20 sec

Test stats 🧪

Test	Results
Failed	0
Passed	22617
Skipped	1937
Total	24554

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