[Prometheus Receiver] Modify existing MetricBuilder to accept unorganized datapoints from Prometheus ScrapeLoop

[PaurushGarg]

Describe the bug
Existing OTEL Prometheus Receiver metricBuilder expects Prometheus scrape loop to send data-points organized and grouped by metricName. Currently, Prometheus doesn’t provide data-point organized and grouped by metric name for failed scrapes, and this causes non-deterministic generation of metrics by the metric builder for the failed scrapes.

Describe the solution you'd like
Currently, metricBuilder aggregates the metric data-points until new metricFamily is encountered. And upon encountering new metricFamily it converts the aggregated data-points into the metric.
This approach causes non-deterministic output upon encountering data-points that are in random order.
As per Prometheus, it is valid but rare for scrape loop to send metrics in random order even for successful scrapes.
One proposed solution is to modify the metricBuilder logic to buffer (aggregate) and sort the datapoints in AddDataPoint method and completely move the metric building logic to the commit logic.

Additional context
Related to open-telemetry/wg-prometheus#57
Issues: #6000 #6087
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.