* Disable VerifyDTDProcessingIsDisabled2

* Update src/Build.UnitTests/Evaluation/Evaluator_Tests.cs

Updates some packages to more recent versions. Coordinates with Roslyn
and VS changes to do the same.

To match the version we're shipping as of b362620.

* Add Change Wave 17.2

Co-Authored-By: Forgind <Forgind@users.noreply.github.com>

* Use AssemblyDependencyResolver in .NET

* Improved diagnosability in TypeLoader_Tests

* Only use AssemblyDependencyResolver if AssemblyPath exists

* Bump versions

* Look for .deps.json file

* PR feedback

Co-authored-by: Rainer Sigwald <raines@microsoft.com>

* Add NamePattern field to sdk resolver manifest.

* Add changewave 17.3 and move the new sdk-resolving algorithm under it.

* Refactor resolver finding.

* Add new resolving algo.

* Fix tests.

* Fix resolver algo.

* Address comments.

* Add comments.

* Add spec for the new sdk resolvers algo.

* Add PR link to changewaves wiki; adjust a unit test.

* Address comments.

* Update src/Build/BackEnd/Components/SdkResolution/SdkResolverLoader.cs

Co-authored-by: Rainer Sigwald <raines@microsoft.com>

* Fix MSBuildToolsDirectoryRoot when BuildEnvironmentMode is None.

* Prefer manifest file over assembly.

* Address some feedback - 1.

* Address some feedback - 2.

* Update event-source.md

* Update my exceptions.

* address comments

Co-authored-by: Rainer Sigwald <raines@microsoft.com>

…operties (#6928)" (#7642)

This caused a regression in scenarios using Visual Studio 17.3 previews
with `global.json` files pointing to old .NET SDKs.

This reverts commit fe4fde9.

Conflicts:
	src/Framework/ChangeWaves.cs
	src/Tasks/CombineTargetFrameworkInfoProperties.cs

* Update dependencies from https://github.com/dotnet/roslyn build 20220512.19

Microsoft.Net.Compilers.Toolset
 From Version 4.2.0-4.22255.15 -> To Version 4.2.0-4.22262.19

* Update dependencies from https://github.com/dotnet/roslyn build 20220516.5

Microsoft.Net.Compilers.Toolset
 From Version 4.2.0-4.22255.15 -> To Version 4.2.0-4.22266.5

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

Bumps Microsoft.VisualStudio.Setup.Configuration.Interop from 3.1.2196 to 3.2.2146.

---
updated-dependencies:
- dependency-name: Microsoft.VisualStudio.Setup.Configuration.Interop
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [System.Security.Cryptography.Pkcs](https://github.com/dotnet/runtime) from 6.0.0 to 6.0.1.
- [Release notes](https://github.com/dotnet/runtime/releases)
- [Commits](dotnet/runtime@v6.0.0...v6.0.1)

---
updated-dependencies:
- dependency-name: System.Security.Cryptography.Pkcs
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Enable registry properties

On non-Windows OSes, return empty, as we had been doing in .NET Core
before.

This enables more project types to evaluate and match .NET Framework
MSBuild's results when on Windows.

* Enable GetRegistryValue* property functions

While looking at registry properties I noticed these were also disabled.
Same logic applies for enabling them.

Since `ProcessStartInfo.Environment` is now available in all supported TFMs,
the feature flag is now just obsolete and even more so an unnecessary
difference between core and framework versions of msbuild.