[exporter/prometheusremotewrite] respect integer exemplar values

[perebaj]

Description

Fixing when exemplars receive values that aren't doubles

Link to tracking issue

Fixes #36657

[perebaj]

I basically copy/paste the content of this function ⬇️

opentelemetry-collector-contrib/pkg/translator/prometheusremotewrite/testutils_test.go

Line 187 in dd600c1

func getHistogramDataPointWithExemplars(t *testing.T, time time.Time, value float64, traceID string, spanID string, attributeKey string, attributeValue string) pmetric.HistogramDataPoint {

But changing the signature to receive an int64 value instead of a float64 one. Does this make sense?

I'm also added a comment in the top of the function, but I notice that most of the private functions doesn't have a comment, should I keep it?

[ArthurSens]

Maybe this is a good use case for generics?

func getHistogramDataPointWithExemplars[V int64 | float64](t *testing.T, time time.Time, value V, traceID string, spanID string, attributeKey string, attributeValue string) pmetric.HistogramDataPoint {
.
.
.
    switch V.(type) {
    case int64:
        e.SetIntValue(value)
    case float64:
        e.SetDoubleValue(value)
    }
.
.
.
}

We could avoid a little bit of code and the change is not thaaaat big to the original function

[perebaj]

7644383

I removed the new helper function that I created, and I added the generic that you mentioned in the existing function

[ArthurSens]

Nice, the only thing left is a changelog entry. When doing a release of this project we compile all files located in this folder. You can copy one as an example, change it to represent what is being fixed in this PR, and commit :)

[perebaj]

Hey guys @ArthurSens @dashpole, feel free to tag me in any kind of issue that you think would be interesting to solve

I'm open to help and learn more about this ecosystem! 🙃

[evan-bradley]

Thanks @perebaj!