ci: use GitHub actions

[v1v]

What

Transition the CI pipeline in Jenkins to GitHub actions

Actions

• Agree the CI workflow
• narrow down the tests for the TAV per module

Checklist

• Implement code
• Add tests
• Update TypeScript typings
• Update documentation
• Add CHANGELOG.asciidoc entry
• Commit message follows commit guidelines

[apmmachine]

💚 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: 2023-01-25T11:13:43.331+0000

• Duration: 18 min 59 sec

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run module tests for <modules> : Run TAV tests for one or more modules, where <modules> can be either a comma separated list of modules (e.g. memcached,redis) or the string literal ALL to test all modules

• run benchmark tests : Run the benchmark test only.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[v1v]

For simplicity, I'll close this PR and raise one per stage, so it's easier to roll out GH actions, PRs:

• action: snapshoty #3125
• action: edge #3126
• action: tav #3127
• action: lint and ELASTIC_APM_CONTEXT_MANAGER=patch #3128