[Prometheus Receiver] Add test to validate metrics renaming as per configuration

[PaurushGarg]

Is your feature request related to a problem? Please describe.
In order to verify that the Prometheus receiver is functioning as expected, a new test is needed to verify that Prometheus receiver renames the metric as per metric_relabel_configs configuration provided in scrap_configs of Prometheus Receiver configuration in OTEL collector configuration yaml file.
Create testcases for:

• Metrics renaming using relabel.Action for replace, drop, and keep.
• Labels renaming using relabel.Action replace, drop, keep, and hashmod.

Describe the solution you'd like
Prometheus Receiver should rename the metric and labels as per metric_relabel_configs configuration.
Create testdata for Prometheus Receiver to scrape and provide renaming configuration for each relabel.Action in Promethues Receiver configuration . For example:

receivers:
  prometheus:
    config:
      scrape_configs:
      - job_name: rename
        scrape_interval: 5s
        static_configs:
         - targets: [ "localhost: 4567" ]
        metric_relabel_configs:
        # rename otelcol_process_cpu_seconds to process_cpu_seconds by replacing the __name__ label 
          - source_labels: [ __name__ ]
            regex: "otelcol_(.*)"
            action: replace
            target_label:  __name__
            replacement: "$1"

Expected Behavior:
Prometheus Receiver renames the metrics as per the given configuration. To validate, assert that the metric name has been renamed. In addition, similar to metric_receiver_test.go validate the scrapes to ensure correct OTLP data transformation.

Additional context
Related to open-telemetry/wg-prometheus#57

Related Open Issues:
#5001
cc: @alolita @Aneurysm9

[PaurushGarg]

@alolita please assign this issue to me. I would like to work on this one.

[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.