[configcompression] Mark as stable

[TylerHelmuth]

Description:
Mark configcompression as Stable

Link to tracking Issue:
Closes #9374

[mx-psi]

cc @open-telemetry/collector-approvers

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.90%. Comparing base (94ae776) to head (9b22b4f).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9571   +/-   ##
=======================================
  Coverage   90.90%   90.90%           
=======================================
  Files         348      348           
  Lines       18384    18384           
=======================================
  Hits        16712    16712           
  Misses       1348     1348           
  Partials      324      324           

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

[atoulme]

LGTM, checked the code and test coverage.

[bogdandrutu]

I would personally prefer to stabilize modules in the order of possible dependencies (see #9491) and not mark random modules as stable before we have all the basic modules stable.

[mx-psi]

@bogdandrutu This module does not have any explicit dependency to confmap, consumer or component, and I think the only thing we are assuming from these modules is that we will honor the encoding.TextUnmarshaler interface when unmarshaling configuration.

I don't see us changing this assumption, since this is a Go stdlib interface, but if you think we may change this or you have a different specific concern, I would want to have an issue for it.