feat(telemetry): export ExtraConfig and CosmosExtra types

[gjermundgaraba]

• Export extraConfig → ExtraConfig and cosmosExtra → CosmosExtra so external consumers can programmatically construct the cosmos_extra section of otel.yaml without maintaining manual YAML templates
• Adds godoc comment to ExtraConfig explaining intended usage alongside otelconf.OpenTelemetryConfiguration

[aaronc]

These types should be considered highly unstable, thus the reason they're not exported. But I guess with v0.x versioning that doesn't matter. Ideally, otelconf supports all this stuff natively eventually

[gjermundgaraba]

These types should be considered highly unstable, thus the reason they're not exported. But I guess with v0.x versioning that doesn't matter. Ideally, otelconf supports all this stuff natively eventually

True, but these types are practically exposed to the user anyway, so it makes sense to make the available for automation. I would rather have compilation errors than having to manually keep this in sync.

[aaronc]

Fair enough. We might want to give the types slightly better names

[codecov]

Codecov Report

❌ Patch coverage is 0% with 14 lines in your changes missing coverage. Please review.
✅ Project coverage is 59.78%. Comparing base (2c139bd) to head (5f4cf2c).

Files with missing lines	Patch %	Lines
telemetry/config.go	0.00%	14 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #26006      +/-   ##
==========================================
- Coverage   59.80%   59.78%   -0.02%     
==========================================
  Files         965      965              
  Lines       64229    64227       -2     
==========================================
- Hits        38410    38397      -13     
- Misses      25819    25830      +11     

Files with missing lines	Coverage Δ
telemetry/config.go	2.38% <0.00%> (+0.05%)	⬆️

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[gjermundgaraba]

@aaronc @aljo242 I made an attempt at a more descriptive name. Not sure if you want to keep the cosmos_extra yaml name or not. Let me know if you like the name, and what to do about the yaml field.

[technicallyty]

could you update the readme and the example config there too?

[technicallyty]

@aaronc @aljo242 I made an attempt at a more descriptive name. Not sure if you want to keep the cosmos_extra yaml name or not. Let me know if you like the name, and what to do about the yaml field.

how about just extensions for both yaml and the custom struct

[gjermundgaraba]

could you update the readme and the example config there too?
Done!

@aaronc @aljo242 I made an attempt at a more descriptive name. Not sure if you want to keep the cosmos_extra yaml name or not. Let me know if you like the name, and what to do about the yaml field.

how about just extensions for both yaml and the custom struct
Updated, let me know what you think?

[technicallyty]

lgtm, thanks!

Fixed