[exporterhelper] Implement new component-identifying attributes

[jade-guiton-dd]

The Pipeline Component Telemetry RFC defines a set of attributes that should be used to describe which component instance a telemetry item comes from.

The exporter attribute on the exporterhelper spans and metrics exposes the component ID, and the span/metric names + data_type span attribute expose the relevant signal, which is enough to identify the component instance. However, this does not follow the RFC's conventions.

To bring things in line with the RFC, we would need to add the following attributes to metrics and spans:

• otelcol.component.kind: always exporter
• otelcol.component.id: the component ID
• otelcol.signal: logs, metrics, traces, profiles

All this information should already be available in the helper, but instead of implementing the attributes manually, I would recommend waiting to see if the pipeline telemetry implementation introduces a general mechanism for getting these attributes.

This would be a step towards the stabilization of the otlpexporter and otlphttpexporter: cf. #11140.

[bogdandrutu]

Few things:

1. The pipeline will not be able to control the spans created when consuming from the queue, since it cannot go into the component implementation.
2. The "queue consumer" span right now, has "exporter"=ID and "data_type"=Signal as attributes, see
   https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/exporterhelper/internal/obs_report.go#L68

[jade-guiton-dd]

1. Can you clarify what you mean by this? This issue is for the exporterhelper to manually set attributes that are passed down to it (probably through TelemetrySettings) on its own internal telemetry, no changes are to be made on the pipeline level.

2. Right sorry, I thought the new span attribute was signal rather than data_type. I updated the PR description.