Stabilize module go.opentelemetry.io/collector/config/configtelemetry

[atoulme]

Before stabilizing a module, an approver or maintainer must make sure that the following criteria have been met for at least two successive minor version releases (regardless of when this issue was opened):

• [ ] No open issues or PRs in the module that would require breaking changes
• [x] No TODOs in the module code that would require breaking changes
• [x] No deprecated symbols in the module
• [x] No symbols marked as experimental in the module
• [x] The module follows the Coding guidelines

Please also make sure to publicly announce our intent to stabilize the module on:

• [x] The #otel-collector CNCF Slack Channel
• [x] The #opentelemetry CNCF Slack channel
• [x] A Collector SIG meeting (if unable to attend, just add to the agenda)

To help other people verify the above criteria, please link to the announcement and other links used to complete the above in a comment on this issue.

Once all criteria are met, close this issue by moving this module to the stable module set.

[atoulme]

Announced on https://cloud-native.slack.com/archives/CJFCJHG4Q/p1717139327041089 and https://cloud-native.slack.com/archives/C01N6P7KR6W/p1717139310969049

[jaronoff97]

Prior to this package's stabilization, I would love it if there were more guidance on what each of the levels are for. Right now the documentation is very vague and I think the differences between normal & detailed are not specific enough. This is almost a flavor of #7543 where that metric could have been enabled only in the "detailed" configuration, however, reserving "detailed" that way wasn't an option because we put many metrics behind "detailed" that I would argue belong more in the "normal" or "basic" levels (ex of a detailed metric that IMO should be a "normal" metric).

[atoulme]

@jaronoff97 opening https://github.com/open-telemetry/opentelemetry-collector/issues/10286

[atoulme]

Announced at SIG meeting 6/5.