Polish OpenTelemetryResourceAttributes

[nosan]

Update OpenTelemetryResourceAttributes to use StringUtils.uriDecode(...), as it provides the same functionality as the custom decode(...) method.

[mhalbritter]

Thanks @nosan !

[nosan]

@mhalbritter

I just found this core issue: spring-projects/spring-framework#34570.

It actually does alter a Unicode character.

Consider the following test:

@Test
void otelResourceAttributes() {
    this.environmentVariables.put("OTEL_RESOURCE_ATTRIBUTES", "key8=%20ś\u2019");
    assertThat(getAttributes()).containsEntry("key8", " ś’");
}

The custom decode method works fine, but StringUtils.uriDecode fails with an error:

Expecting map:
  {"key8"=" [�", "service.name"="unknown_service"}
to contain entries:
  ["key8"=" ś’"]
but the following map entries had different values:
  ["key8"=" [�" (expected: " ś’")]
java.lang.AssertionError: 
Expecting map:
  {"key8"=" [�", "service.name"="unknown_service"}
to contain entries:
  ["key8"=" ś’"]
but the following map entries had different values:
  ["key8"=" [�" (expected: " ś’")]

[mhalbritter]

Hm. We should then stay on the custom decode method until this is fixed. I'll get that fixed.

[nosan]

Thanks, sorry for inconvenience :(

[mhalbritter]

No problem. I've fixed that in 3bd75f6 and subscribed to spring-projects/spring-framework#34570. When that's fixed in Framework, we can use their decode method.