action: use opentelemetry composite action

[v1v]

Motivation/summary

Back in the days we built the Jenkins OTEL integration, so let's use the same approach for the GH actions, so every workflow and step will be tracked as traces/spans.

How to test these changes

See traces in the Elastic deployment

This has been already tested for quite sometime in some other projects

https://github.com/elastic/apm-pipeline-library/blob/main/.github/workflows/opentelemetry.yml

[ghost]

💚 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-17T11:44:47.348+0000

• Duration: 20 min 39 sec

Test stats 🧪

Test	Results
Failed	0
Passed	5079
Skipped	3600
Total	8679

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /test linters : Run the Python linters only.

• /test full : Run the full matrix of tests.

• /test benchmark : Run the APM Agent Python benchmarks tests.

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

[ghost]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (71/71)	💚
Files	100.0% (236/236)	💚
Classes	100.0% (236/236)	💚
Lines	92.073% (18677/20285)	👎 -0.005
Conditionals	75.163% (2878/3829)	👎 -0.026