[receiver/prometheusreceiver] identify telemetry scraped by the prometheus receiver

[mwear]

Is your feature request related to a problem? Please describe.
I would like to be able to tell which metrics are scraped by the prometheus receiver.

Describe the solution you'd like
Most receivers set the scope name to the receiver name (e.g. otelcol/postgresqlreceiver). The most straightforward solution would be to set the scope name to otelcol/prometheusreceiver.

Describe alternatives you've considered
If scope.name is reserved for other use with the prometheus receiver, we could use a different scope attribute, or even a resource attribute.

Additional context

• Possibly related to: Add Instrumentation Scope and Version as labels in Prometheus opentelemetry-specification#2703
• Loosely related to: Improve Prometheus receiver observability #4973

[github-actions]

Pinging code owners: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/prometheus: @Aneurysm9 @dashpole

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[atoulme]

See #20902 as duplicate.

[paologallinaharbur]

I think we can close this since this #20903 has been merged