action: update specs

[v1v]

What

Use GitHub actions in addition to the updatecli to bump the json schemas created in ecs-logging.

It runs on a daily basis and create a Pull Request if new changes exist.

Create PRs with the description pointing to the original change in the ecs-logging, similarly done in elastic/ecs-logging-ruby#30

Why

Jenkins ecosystem at Elastic is deprecated, so let's use GH actions with updatecli, so consumers can control what to do and when.

Further details

The automation relied on Jenkins and projects were onboarded by having a configuration entry in https://github.com/elastic/ecs-logging/blob/main/.ci/.jenkins-loggers.yml

[v1v]

I created the specs.json empty file so we can validate the automation works as expected when this PR is merged

[apmmachine]

💔 Build Failed

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-02-08T17:28:04.119+0000

• Duration: 6 min 27 sec

Test stats 🧪

Test	Results
Failed	0
Passed	6
Skipped	0
Total	6

Steps errors

Expand to view the steps failures

Run tests

• Took 0 min 1 sec . View more details here
• Description: VERSION=7.2-alpine composer test

Run tests

• Took 0 min 1 sec . View more details here
• Description: VERSION=7.3-alpine composer test

Run tests

• Took 0 min 1 sec . View more details here
• Description: VERSION=7.4-alpine composer test

Run tests

• Took 0 min 1 sec . View more details here
• Description: VERSION=8.0-alpine composer test

Error signal

• Took 0 min 0 sec . View more details here
• Description: hudson.AbortException: script returned exit code 2

🤖 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 elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)