New otelcol.exporter.debug component

[ptodev]

PR Description

The debug exporter is a replacement for the logging exporter. This exporter was also added to the Agent.

PR Checklist

• CHANGELOG.md updated
• Documentation added
• Tests updated
• Config converters updated

[wildum]

Do you think that we need this component now that we have the live debugging feature which supports all otel receivers and processors?
This component: shows only the output of the pipeline, the data is mixed with logs from Alloy, it has sample rate and verbosity features
Live debugging: can show the output of any steps in the pipeline without modifying the original pipeline, the data is separated from Alloy's logs, it has filtering, sample rate, pause/unpause, copy to clipboard features. For the cons the user needs an access to the UI and it's an experimental feature still

[ptodev]

@wildum I agree that in the long term we should recommend that people use Live Debugging. However, I think there will always be a need for us to have this exporter:

• The logs it produces could be sent to Loki
• It's a useful component for the upstream Collector, and folks who are used to it might want to still use it. They might have already established processes around this.
• It might be necessary for some config conversions between upstream yaml and Alloy syntax.

In the long term, I think we should keep this component but we can have a banner in the docs that recommends Live Debugging instead.

[clayton-cornell]

Docs look OK to me now. :-)

[wildum]

LGTM, just one nit