Update nuget packages

[CleanCodeDeveloper]

Summary of the Pull Request

What is this about:
Updating nuget packages to latest version.

What is included in the PR:
Nuget package upgrade for csproj files (i did not touch *.vcxproj).

This is how it looks now:

All nuget packages on the screenshot are in vcxproj except UnitsNet, Mircosoft.UI.Xaml, System.IO.Abstractions. Those packages had a few breaking changes and should be updated in a separate PR.

Binaries:

Added:
5x System.Text.Json.dll

Removed:
1x Microsoft.Extensions.Configuration.dll
1x Microsoft.Extensions.Configuration.Binder.dll

How does someone test / validate:
Updating dependencies can be dangerous. Please test carefully.

Quality Checklist

• Linked issue: Update from .net framework 5 to .net framework 6 #16088
• Communication: I've discussed this with core contributors in the issue.
• Tests: Added/updated and all pass
• Installer: Added/updated and all pass
• Localization: All end user facing strings can be localized
• Docs: Added/ updated
• Binaries: Any new files are added to WXS / YML
  • No new binaries
  • YML for signing for new binaries
  • WXS for installer for new binaries

Contributor License Agreement (CLA)

A CLA must be signed. If not, go over here and sign the CLA.

[stefansjfw]

We had issues with some tests not being run when we tried updating

    <PackageReference Include="MSTest.TestAdapter" Version="2.2.3" />
    <PackageReference Include="MSTest.TestFramework" Version="2.2.3" />

We need to see if that's resolved..

Also updating Microsoft.UI.Xaml had additional dependencies with newer versions. Let's just be careful here

[stefansjfw]

Yeah, the same group of tests is still not being run with later versions of TestAdapter and TestFramework (> 2.2.3)

[CleanCodeDeveloper]

We had issues with some tests not being run when we tried updating

    <PackageReference Include="MSTest.TestAdapter" Version="2.2.3" />
    <PackageReference Include="MSTest.TestFramework" Version="2.2.3" />

We need to see if that's resolved..

I first though it would be a local issue on my machine. I downgraded to 2.2.3 and can run all the tests again.

It would be great if someone from Microsoft who works on the MSTest.* library chimes in and explains what's going on. Never had any issues with these libraries until they version 2.2.4.

Also updating Microsoft.UI.Xaml had additional dependencies with newer versions. Let's just be careful here

Microsoft.UI.Xaml was tricky too. 2.7.0 does not work but 2.7.1-preview seems to be fine.

[crutkas]

sending the signing agent against to just validate

[stefansjfw]

tested. looks good. Thanks for contribution!

[jaimecbernardo]

Microsoft.UI.Xaml was tricky too. 2.7.0 does not work but 2.7.1-preview seems to be fine.

This is because of our use of XAML islands. Only prerelease versions of Microsoft.UI.XAML have support for it.

Thanks a lot for the contribution!