Reduce cardinality of traces/spans for running tests

[mdelapenya]

We are currently creating a span per test (https://github.com/mdelapenya/junit2otlp/blame/ede48c1865c6a23ce58bf03dfb4fca3c913f0cb5/main.go#L119) and per test suite (https://github.com/mdelapenya/junit2otlp/blame/ede48c1865c6a23ce58bf03dfb4fca3c913f0cb5/main.go#L99) which leads to have different spans per test name and test suite, increasing the cardinality of those spans.

I'd suggest decreasing it naming both spans as run-test and run-suite (or similar) and declaring the test name and test suite name as an attribute of the span.

@v1v @cyrille-leclerc @kuisathaverat wdyt?

[kuisathaverat]

In the Jenkins OpenTelemetry plugin, we have had the same issue, the problem is that if you move the name of the test to an attribute you will not differentiate them in the UI.

jenkinsci/opentelemetry-plugin#271
jenkinsci/opentelemetry-plugin#260
jenkinsci/opentelemetry-plugin#47