[9.0](backport #6713) [otel] Update OTel components to v0.119.0

[mergify]

What does this PR do?

Updates OTel components to v0.119.0.

Why is it important?

We should be keeping the components up to date with upstream.

Checklist

• 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

go build . sudo ./elastic-agent otel ```<hr>This is an automatic backport of pull request #6713 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 61771d7 has failed:

On branch mergify/bp/9.0/pr-6713 Your branch is up to date with 'origin/9.0'. You are currently cherry-picking commit 61771d763. (fix conflicts and run "git cherry-pick --continue") (use "git cherry-pick --skip" to skip this patch) (use "git cherry-pick --abort" to cancel the cherry-pick operation) Changes to be committed:	modified: NOTICE.txt	new file: changelog/fragments/1738752554-update-otel-v0.119.0.yaml Unmerged paths: (use "git add <file>..." to mark resolution)	both modified: go.mod	both modified: go.sum	both modified: internal/pkg/otel/README.md 

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[elasticmachine]

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

[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