ci: automatically update OTel components

[andrzej-stencel]

What does this PR do?

Creates a new Updatecli configuration to check if a new version of OTel Collector components is available. If it is, Updatecli runs the update-otel.sh script and creates a new PR with the changes.

Also creates a new GitHub Actions workflow to trigger the Updatecli configuration daily. The workflow is configured torun for the main branch and for the 8.19 branch.

Why is it important?

We want to be on the latest version of OTel Collector components on main and 8.19 branches. We already had a script to update OTel dependencies that took as parameters the versions to update to. What this PR adds is checking for latest OTel versions online and triggering the script if an update is required.

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added an entry in ./changelog/fragments using the changelog tool
• [ ] I have added an integration test or an E2E test

How to test this PR locally

BRANCH_NAME=main updatecli diff --config ./.ci/updatecli/update-otel.yml

This will succeed locally if you remove the references to SCM from the file .ci/updatecli/update-otel.yml: scms, conditions.is-new-version.scmid, actions.

Related issues

• Closes Update all OTel upstream dependencies regularly and atomically #6132

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[mergify]

This pull request does not have a backport label. Could you fix it @andrzej-stencel? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[v1v]

To test locally against the main branch, you can use the below snippet (as long as you have gh locally):

$ gh pr checkout 8288
$ GITHUB_TOKEN=$(gh auth token) \
  GITHUB_ACTOR=v1v \
  BRANCH_NAME=main updatecli diff \
    --config ./.ci/updatecli/update-otel.yml 
    --values .ci/updatecli/values.d/scm.yml


+++++++++++
+ PREPARE +
+++++++++++
[..]


condition: condition#is-new-version
------------------------
The shell 🐚 command "/bin/sh /var/folders/t7/ghqdh8cx2g12pwb_w0ncmw900000gn/T/updatecli/bin/b8e0f34aa6b0f3e4759c4ad975a6de8175acea171186f323dc1c3c345e68a176.sh" exited on error (exit code 1) with the following output:
----
----

command stderr output was:
----
----
shell command failed. Expected exit code 0 but got 1
✗ shell condition of type "console/output" not passing

target: target#update-otel
------------------


ACTIONS
========

No target found for action "default"

=============================

SUMMARY:



- Update OTel:
	Source:
		✔ [current_contrib] Get current OTel Collector contrib version in go.mod
		✔ [current_core_beta] Get current OTel Collector core beta version in go.mod
		✔ [latest_contrib] Get latest OTel Collector contrib version
		✔ [latest_core_beta] Get latest OTel Collector core beta version
		✔ [latest_core_stable] Get latest OTel Collector core stable version
	Condition:
		✗ [is-new-version] Succeeds if the latest core or contrib OTel Collector version is different than the one in go.mod
	Target:
		- [update-otel] 


Run Summary
===========
Pipeline(s) run:
  * Changed:	0
  * Failed:	0
  * Skipped:	1
  * Succeeded:	0
  * Total:	1

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b update-otel-automatically upstream/update-otel-automatically
git merge upstream/main
git push upstream update-otel-automatically

[v1v]

Thanks

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b update-otel-automatically upstream/update-otel-automatically
git merge upstream/main
git push upstream update-otel-automatically

[v1v]

LGTM, just a question about where the updatecli pipeline needs to be defined