Support resource detectors for service telemetry

[iblancasa]

Description

Support resource detectors for service telemetry using Go SDK.

Link to tracking issue

Fixes #14311

[codecov]

Codecov Report

❌ Patch coverage is 58.60870% with 238 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.62%. Comparing base (ff135af) to head (f66cd1e).

Files with missing lines	Patch %	Lines
service/internal/resource/config.go	59.09%	149 Missing and 31 partials ⚠️
service/telemetry/otelconftelemetry/sdk.go	21.05%	29 Missing and 1 partial ⚠️
service/telemetry/otelconftelemetry/resource.go	29.41%	24 Missing ⚠️
service/internal/resource/detectors.go	93.65%	2 Missing and 2 partials ⚠️

❌ Your patch check has failed because the patch coverage (58.60%) is below the target coverage (95.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14312      +/-   ##
==========================================
- Coverage   92.12%   91.62%   -0.51%     
==========================================
  Files         668      669       +1     
  Lines       41377    41924     +547     
==========================================
+ Hits        38120    38414     +294     
- Misses       2222     2436     +214     
- Partials     1035     1074      +39     

☔ 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.

[codspeed-hq]

CodSpeed Performance Report

Merging this PR will not alter performance

_{Comparing iblancasa:14311 (f66cd1e) with main (ff135af)}

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

Summary

✅ 59 untouched benchmarks
⏩ 20 skipped benchmarks¹

Footnotes

1. 20 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[dmathieu]

This PR does a lot of things. I think it would be better split into smaller chunks.

[dmathieu]

This is unrelated to your PR. Could you move it to another one?

[iblancasa]

The problem is that, without this, the tests fails now.

[dmathieu]

That seems like a problem we want to fix rather than walk around. Especially as a 10 minutes timeout is very long.

[iblancasa]

This PR does a lot of things. I think it would be better split into smaller chunks.

Let me see what I can do.