Migrate specs update to updatecli

[reakaleek]

What

Migrate https://github.com/elastic/apm/blob/main/.ci/Jenkinsfile to the consumer using updatecli and GH Actions workflows.

Why

Jenkins 2 GH Actions Migration

How to test

export GITHUB_TOKEN="<your-personal-access-token>"
export GIT_USER="FooBar"
export GIT_EMAIL="foo@bar.com"
updatecli --config .ci/updatecli.d/update-json-specs.yml diff
updatecli --config .ci/updatecli.d/update-gherkin-specs.yml diff

[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-03-30T06:10:03.792+0000

• Duration: 3 min 19 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 benchmark tests : Run the benchmark test.

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

[axw]

This is probably fine, but is it possible to specify a directory and keep them synchronised, like an rsync?

[reakaleek]

This is probably fine, but is it possible to specify a directory and keep them synchronised, like an rsync?

Unfortunately, not. There was a similar request/question here: elastic/apm-agent-nodejs#3197 (comment)

[axw]

@reakaleek no worries.

We're requiring commits to be signed now, so please squash, sign, and force-push.

[v1v]

Otherwise

WARNING: **Fallback** Please add a title to you configuration using the field 'title: <your pipeline>'
Pipeline "update-jsons-specs" failed
Skipping due to:
	action stage:	"Title is too long (maximum is 256 characters)"