[consumer] Mark module as stable

[mx-psi]

Description

Mark consumer module as stable. This is now possible after #11491, since consumererror is a separate module now.

Link to tracking issue

Fixes #9046

[mx-psi]

cc @open-telemetry/collector-approvers

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.48%. Comparing base (f2b31d1) to head (e94d27e).
Report is 48 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #11492   +/-   ##
=======================================
  Coverage   91.48%   91.48%           
=======================================
  Files         433      433           
  Lines       23617    23617           
=======================================
  Hits        21607    21607           
  Misses       1642     1642           
  Partials      368      368           

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

[bogdandrutu]

I would merge this after the release to not rush it. Are we ok with that?

[mx-psi]

I would merge this after the release to not rush it. Are we ok with that?

Definitely, and regardless of the release let's at least wait for a few days at least in case somebody has an objection

[jade-guiton-dd]

It seems that the current API only permits passing signal-agnostic Options to NewLogs/NewMetrics/NewTraces. How sure are we that we will never need or want to implement consumer options that are specific to one particular signal? (As a hypothetical and possibly impractical example, what if once tracing is integrated to the consumer module (#8804), we want to specify attributes from consumed metrics to be included as part of the trace?)

[mx-psi]

Fromt he 2024-10-28 Collector stability meeting, @bogdandrutu will take a look and see if we should do #11492 (comment)