actions: run check for x-pack/packetbeat and packebeat

[v1v]

What does this PR do?

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

What's the check stage?

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

Why is it important?

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

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.

Solved Issues

pcap.h: No such file or directory

# github.com/google/gopacket/pcap
Error: ../../../../go/pkg/mod/github.com/elastic/gopacket@v1.1.20-0.20211202005954-d412fca7f83a/pcap/pcap_unix.go:[34](https://github.com/elastic/beats/runs/7875203008?check_suite_focus=true#step:5:35):10: fatal error: pcap.h: No such file or directory
   34 | #include <pcap.h>
      |          ^~~~~~~~
compilation terminated.
Error: failed running go vet, please fix the issues reported: running "go vet ./..." failed with exit code 2
make: *** [../libbeat/scripts/Makefile:153: check] Error 1
make: Leaving directory '/home/runner/work/beats/beats/packetbeat'
Error: Process completed with exit code 2.

Solved with a315907

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

Follow ups

If agreed then we can roll out this approach for the remaining beats

[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-17T09:15:51.355+0000

• Duration: 49 min 4 sec

Test stats 🧪

Test	Results
Failed	0
Passed	1672
Skipped	19
Total	1691

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

[v1v]

When changes in those files

[v1v]

Then run make

[v1v]

When changes in these files