Bump OpenTelemetry to 1.60.1

[reta]

Description

Bump OpenTelemetry to 1.60.1

Related Issues

N/A

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

PR Reviewer Guide 🔍

(Review updated until commit cd0f3d4)

Here are some key observations to aid the review process:

🧪 No relevant tests

🔒 No security concerns identified

✅ No TODO sections

🔀 No multiple PR themes

⚡ Recommended focus areas for review SHA1 Verification The SHA1 checksums for all updated OpenTelemetry JARs should be verified against the official Maven Central repository to ensure the artifacts have not been tampered with. Each new .sha1 file should be cross-checked with the published checksums. 67a515491f676e9ac9719839a97cbde7b1ffc2c2

[github-actions]

PR Code Suggestions ✨

Latest suggestions up to cd0f3d4
Explore these optional code suggestions:

Category	Suggestion	Impact
General	Add missing trailing newline to SHA1 files SHA1 files should end with a newline character for POSIX compliance and to avoid issues with tools that read these files. All new .sha1 files in this PR are missing a trailing newline (indicated by \ No newline at end of file). Add a newline at the end of each SHA1 file. plugins/telemetry-otel/licenses/opentelemetry-api-1.60.1.jar.sha1 [1] +67a515491f676e9ac9719839a97cbde7b1ffc2c2 - Suggestion importance[1-10]: 2 __ Why: The existing_code and improved_code are identical, making this suggestion impossible to evaluate as a concrete change. Additionally, looking at the diff, the new .sha1 files do appear to have content on line 1 followed by line 2 (empty), suggesting a newline may already be present. The suggestion is also low-impact for SHA1 checksum files.	Low

---

Previous suggestions

Suggestions up to commit f77f64a

Category	Suggestion	Impact
General	Add missing trailing newline to SHA1 files SHA1 files should end with a newline character for POSIX compliance and to avoid issues with tools that read these files. All new .sha1 files in this PR are missing a trailing newline (indicated by \ No newline at end of file). Add a newline at the end of each SHA1 file. plugins/telemetry-otel/licenses/opentelemetry-api-1.60.1.jar.sha1 [1] +67a515491f676e9ac9719839a97cbde7b1ffc2c2 - Suggestion importance[1-10]: 2 __ Why: The existing_code and improved_code are identical, making this suggestion impossible to evaluate as a concrete change. Additionally, looking at the diff, the new .sha1 files do appear to have content on line 1 followed by line 2 (blank), suggesting a newline may already be present. The suggestion is also low-impact for SHA1 checksum files.	Low

[github-actions]

❌ Gradle check result for f77f64a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

Persistent review updated to latest commit cd0f3d4

[github-actions]

✅ Gradle check result for cd0f3d4: SUCCESS

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.13%. Comparing base (91baf0b) to head (cd0f3d4).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #20797      +/-   ##
============================================
- Coverage     73.22%   73.13%   -0.09%     
+ Complexity    72109    72005     -104     
============================================
  Files          5794     5794              
  Lines        329806   329806              
  Branches      47593    47593              
============================================
- Hits         241490   241219     -271     
- Misses        68932    69222     +290     
+ Partials      19384    19365      -19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.