Version updates for most packages to latest versions

[bwadswor]

AzureCoreVersion 1.35.0 -> 1.36.0
AzureIdentityVersion 1.10.2 -> 1.10.4
MicroBuildCoreVersion 0.2.0 -> 0.3.1
MicrosoftNETCorePortableCompatibilityVersion 1.0.1 -> 1.0.2
MicrosoftIdentityClientVersion 4.54.1 -> 4.58.1
MicrosoftIdentityClientExtensionsMsalVersion 2.31.0 -> 4.58.1
MicrosoftIdentityModelTokensVersion 6.22.0 -> 7.1.2
MicrosoftIdentityModelJsonWebTokensVersion 6.22.0 -> 7.1.2
MicrosoftSourceLinkGitHubVersion 1.1.1 -> 8.0.0
MicrosoftWin32RegistryVersion 4.4.0 -> 5.0.0
SystemCollectionsImmutableVersion 1.7.1 -> 8.0.0
SystemDiagnosticsDiagnosticSourceVersion 6.0.1 -> 8.0.0
SystemMemoryVersion 4.5.4 -> 4.5.5
SystemReflectionMetadataVersion 1.8.1 -> 8.0.0
SystemReflectionTypeExtensionsVersion 4.3.0 -> 4.7.0
SystemRuntimeVersion 4.3.0 -> 4.3.1
SystemSecurityCryptographyAlgorithmsVersion 4.3.0 -> 4.3.1
SystemTextEncodingsWebVersion 4.7.2 -> 8.0.0
SystemTextJsonVersion 4.7.2 -> 8.0.1

[cincuranet]

I think we should take this is steps. First in patch versions updates, which should be fairly safe. Then minor and then finally major version updates. Together with increased amount of testing/tests. What do you think @brianrob?

[brianrob]

I'm thinking that we should ultimately do one "test pass" - we'll need to figure out what areas are likely to be impacted. We can also do some dogfooding as well prior to release. We could break this up into patch vs. others, but I'm not sure there is benefit if we think the risk of patch is low - it's not necessary to immediately make the changes, so it's OK if they get merged with the rest.

I do think that it would be worthwhile to break the commit into the categories that you've described above so that if (when) we do miss an issue, we'll have a better git-bisect experience. How does that sound?

[cincuranet]

Yeah, definitely smaller commits.

[brianrob]

I have updated this with some smaller commits. Will do some testing and if all goes well, will merge.