Return consumererror.Permanent in the Prometheus remote write exporter

[huyan0]

The Prometheus remote write exporter right now returns vanilla Go errors. This breaks the retry mechanism in the Collector. If a batch contains a metric with invalid temporailty or it gets a 400 response code from the backend, the collector will exponentially backoff and retry, getting the same error every time.

If the Prometheus remote write returns error of consumererror.Permanent type, the retry mechanism will not be triggered

cc: @bogdandrutu @alolita @huyan0

[huyan0]

I am working on a PR to fix this.

[amanbrar1999]

I will pick up this issue

-cc @alolita @bogdandrutu @jmacd @tigrannajaryan

[amanbrar1999]

This issue should be resolved from my latest PR

@tigrannajaryan you can either assign it to me or close it, Yang no longer works on this project

[andrewhsu]

from the issue triage session at the collector sig, looks like this is done so closing