fix(resources): strict OTEL_RESOURCE_ATTRIBUTES decoding

[legendecas]

Which problem is this PR solving?

Fixes #3131

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• Add new valid test cases
• Add new invalid test cases

Checklist:

• Followed the style guidelines of this project
• Unit tests have been added
• Documentation has been updated

[codecov]

Codecov Report

Merging #3341 (7986767) into main (e9347e4) will increase coverage by 0.84%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3341      +/-   ##
==========================================
+ Coverage   92.68%   93.53%   +0.84%     
==========================================
  Files         237      244       +7     
  Lines        6921     7394     +473     
  Branches     1443     1532      +89     
==========================================
+ Hits         6415     6916     +501     
+ Misses        506      478      -28     

Impacted Files	Coverage Δ
...entelemetry-resources/src/detectors/EnvDetector.ts	94.11% <100.00%> (+5.88%)	⬆️
...emetry-instrumentation-xml-http-request/src/xhr.ts	97.58% <0.00%> (ø)
...ation-xml-http-request/src/enums/AttributeNames.ts	100.00% <0.00%> (ø)
...es/opentelemetry-context-zone-peer-dep/src/util.ts	100.00% <0.00%> (ø)
...-instrumentation-fetch/src/enums/AttributeNames.ts	100.00% <0.00%> (ø)
...mentation-xml-http-request/src/enums/EventNames.ts	100.00% <0.00%> (ø)
...s/opentelemetry-instrumentation-fetch/src/fetch.ts	97.02% <0.00%> (ø)
...ry-context-zone-peer-dep/src/ZoneContextManager.ts	85.18% <0.00%> (ø)
packages/opentelemetry-sdk-trace-web/src/utils.ts	95.00% <0.00%> (+29.37%)	⬆️

[anthony-telljohann]

I didn't realize characters outside the baggage-octet range MUST be percent-encoded. Great fix.

[dyladan]

I didn't realize characters outside the baggage-octet range MUST be percent-encoded. Great fix.

The baggage specification is actually going to remove that wording. The spec will simply state the character range which is allowed and suggest percent encoding as one possible way to stay within the allowed character range.

source: I am on the working group which made the decision

[dyladan]

lint failure caused by shields.io. rerunning but it isn't a blocker