[9.0] Update OTel components to v0.120.x

[swiatekm]

What does this PR do?

Updates OTel components to v0.120.0 in the 9.0 branch. The update for other branches in #6912 is currently blocked. We've unblocked it in 9.0 through #7023, because it blocks other changes that need to land for 9.0 release.

Why is it important?

It unblocks #6937, which should be in 9.0.

Checklist

• I have read and understood the pull request guidelines of this project.
• I have made corresponding changes to the documentation
• I have added an entry in ./changelog/fragments using the changelog tool

[elasticmachine]

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

[swiatekm]

Got a K8s test failure:

=== Failed
=== FAIL: testing/integration TestOtelKubeStackHelm/helm_kube-stack_operator_standalone_agent_kubernetes_privileged (334.06s)
    otel_helm_test.go:122:
        	Error Trace:	/opt/buildkite-agent/builds/bk-agent-prod-gcp-1740576462608313681/elastic/elastic-agent-extended-testing/testing/integration/otel_helm_test.go:122
        	            				/opt/buildkite-agent/builds/bk-agent-prod-gcp-1740576462608313681/elastic/elastic-agent-extended-testing/testing/integration/otel_helm_test.go:96
        	Error:      	Condition never satisfied
        	Test:       	TestOtelKubeStackHelm/helm_kube-stack_operator_standalone_agent_kubernetes_privileged
        	Messages:   	at least 4 agent containers should be checked
=== FAIL: testing/integration TestOtelKubeStackHelm (342.70s)

in https://buildkite.com/elastic/elastic-agent-extended-testing/builds/7694#01954270-d4c5-4926-8442-4861f27bedea.

[swiatekm]

Also got what looks like an ESS problem:

Error: error running test: failed to check for cloud 9.0.0-SNAPSHOT [stack_id: 900-SNAPSHOT, deployment_id: 4711e5467e8d4f109f2ef465fb8535ab] to be ready: context deadline exceeded

[swiatekm]

Got the following error from ogc:

Traceback (most recent call last):
  File "src/gevent/greenlet.py", line 908, in gevent._gevent_cgreenlet.Greenlet.run
  File "/venv/lib/python3.11/site-packages/ogc/deployer.py", line 215, in _up_async
    provisioner.create()
  File "/venv/lib/python3.11/site-packages/ogc/provision.py", line 450, in create
    _nodes = [self.provisioner.create_node(**opts)]  # type: ignore
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/venv/lib/python3.11/site-packages/libcloud/compute/drivers/gce.py", line 4487, in create_node
    self.connection.async_request(request, method="POST", data=node_data)
  File "/venv/lib/python3.11/site-packages/libcloud/common/base.py", line 877, in async_request
    raise LibcloudError("Job did not complete in %s seconds" % (self.timeout))
libcloud.common.types.LibcloudError: <LibcloudError in None 'Job did not complete in 180 seconds'>
2025-02-28T14:03:03Z <Greenlet at 0x7f8dfcbe6ac0: _up_async(<LayoutModel: 2>)> failed with LibcloudError

in https://buildkite.com/elastic/elastic-agent-extended-testing/builds/7768#01954cb3-cb7e-4d39-b24a-62ddfa56530b.

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 27b0e39

Failed CI Steps

• Kubernetes Integration tests

History

• 💔 Build #17846 failed ad23a94
• 💔 Build #17757 failed f05a8fe
• 💔 Build #17611 failed efb374a
• 💔 Build #17563 failed e8e1fef

cc @swiatekm

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube