[Resources.Azure] NugetAudit - fix dependencies with known vulnerabilities

[Kielek]

Follow up to #2034

Changes

    <!-- System.Text.Encodings.Web is indirect reference. It is needed to upgrade it directly to avoid https://github.com/advisories/GHSA-ghhp-997w-qr28 -->
    <PackageReference Include="System.Text.Encodings.Web" Version="4.7.2" />

Changelog based on https://github.com/open-telemetry/opentelemetry-dotnet/blob/37535a5607ee7e4056c0e274ec01d1e0111a64be/src/OpenTelemetry.Exporter.Console/CHANGELOG.md#L112-L114

Merge requirement checklist

• CONTRIBUTING guidelines followed (license requirements, nullable enabled, static analysis, etc.)
• [ ] Unit tests added/updated
• Appropriate CHANGELOG.md files updated for non-trivial changes
• Changes in public API reviewed (if applicable)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.35%. Comparing base (71655ce) to head (f42336c).
Report is 424 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2056      +/-   ##
==========================================
+ Coverage   73.91%   82.35%   +8.43%     
==========================================
  Files         267        6     -261     
  Lines        9615      136    -9479     
==========================================
- Hits         7107      112    -6995     
+ Misses       2508       24    -2484     

Flag	Coverage Δ
unittests-Resources.Azure	82.35% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 273 files with indirect coverage changes

[rajkumar-rangaraj]

The .NET Standard 2.0 version of System.Text.Json has an indirect dependency on System.Text.Encodings.Web. It is better to upgrade System.Text.Json, as was done in OpenTelemetry.Exporter.OneCollector

[rajkumar-rangaraj]

We may need to re-evaluate whether this is still a challenge with auto-instrumentation - #1279 (comment)

[Kielek]

If possible, I would be more conservative with versioning. This solution is applied in Exporter.Console. I do not see any reason we cannot follow this pattern.

[rajkumar-rangaraj]

We will explore it outside of this PR to understand System.Text.Json version could be bumped.