removing the conflicting assembly

[SimaTian]

Fixes microsoft/azure-pipelines-tasks#20734

Context

This is a hopefully temporary rollback due to the assembly collision in Microsoft.IO.Redist

Changes Made

Removed the conflicting dependency.

Testing

Existing tests.

Notes

We have a proper fix here: microsoft/azure-pipelines-tasks-common-packages#422
However since this change is breaking a lot of people, we're doing this as an interim-patch.

[SimaTian]

I've worked with @surayya-MS and @JanProvaznik to check if this is enough to remove the assembly conflict. It appears that this should be sufficient. The current main branch silently fails in windows powershell and works with this change when using the test script

	$Architecture = 'x64'
 
	$Path = "D:\bld\artifacts\bin\bootstrap\net472\MSBuild\Current\Bin\Microsoft.Build.Utilities.Core.dll"
	$msUtilities = [System.Reflection.Assembly]::LoadFrom($Path)

	[type]$t = $msUtilities.GetType('Microsoft.Build.Utilities.ToolLocationHelper')
	if ($t -ne $null) 
	{
		[System.Reflection.MethodInfo] $mi = $t.GetMethod("GetPathToBuildToolsFile",[type[]]@( [string], [string], $msUtilities.GetType("Microsoft.Build.Utilities.DotNetFrameworkArchitecture") ))

	$param3 = $mi.GetParameters()[2]
		$archValues = [System.Enum]::GetValues($param3. ParameterType)


	[object] $archValue = $null
			if ($Architecture -eq 'x86') {
				$archValue = $archValues.GetValue(1) # DotNetFrameworkArchitecture.Bitness32
			} elseif ($Architecture -eq 'x64') {
				$archValue = $archValues.GetValue(2) # DotNetFrameworkArchitecture.Bitness64
			} else {
				$archValue = $archValues.GetValue(1) # DotNetFrameworkArchitecture.Bitness32
			}
		#Write-Host "archValue = $archValue"

	$msBuildPath = $mi.Invoke($null, @( 'msbuild.exe', '17.0', $archValue ))
		$msBuildPath
	}

I've also started exp insertion recommended by @YuliiaKovalova, unless this PR is urgent-urgent I would prefer to wait with the merge until it finishes.