[receivers/prometheusreceiver] ensure that TA scrapeconfigs are merged with statically defined ones

[secustor]

Is your feature request related to a problem? Please describe. The imported code of Prometheus does not work with scrape configs which happen to conflicting each other.
There there has to be a mechanism to prevent this.

Describe the solution you'd like

Describe alternatives you've considered An alternative would be to simply not allow mixed operation of static configs and job retrieval from a target allocator.

Additional context https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/12586#discussion_r935888880

[github-actions[bot]]

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

[dmitryax]

@secustor do you have a chance to work on this issue?

[secustor]

I have some other tasks to do first, so not immediately.

[dmitryax]

Sure, just wanted to see if this can be assigned to you

[github-actions[bot]]

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.

[github-actions[bot]]

This issue has been closed as inactive because it has been stale for 120 days with no activity.