Stabilize module configauth

[mx-psi]

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
• [ ] No TODOs in the module code that would require breaking changes
• [ ] No deprecated symbols in the module
• [ ] No symbols marked as experimental in the module
• [ ] The module follows the Coding guidelines

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

• [ ] The #otel-collector CNCF Slack Channel
• [ ] The #opentelemetry CNCF Slack channel
• [ ] 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.

[bogdandrutu]

Few things I would like to see here:

• Interaction with https://github.com/open-telemetry/opentelemetry-collector/tree/main/client is strange. I would actually want to also clarify what we do with client package. I kind of think that some belongs to consumer and some belongs to extensions like the auth extension.
• Depends on component so it is blocked by the stabilization of component.

[atoulme]

Announced at SIG meeting 3/13.