[vcpkg] Fix vcpkg.targets incorrect output

[JonLiu1993]

Fixes #38502

When building using scripts\buildsystems\msbuild\vcpkg.targets and using Windows PowerShell (rather than PowerShell Core), the build outputs an error message when it actually succeeds.

'pwsh.exe' is not recognized as an internal or external command,

As per @berryzplus' comment on line 229 it incorrectly calls pwsh.exe without checking if pwsh.exe is included in %PATH%

vcpkg/scripts/buildsystems/msbuild/vcpkg.targets

Lines 226 to 231 in ad25766

	<!-- Search %PATH% for pwsh.exe if it is available. -->
	<Exec
	Condition="'$(VcpkgXUseBuiltInApplocalDeps)' != 'true'"
	Command="pwsh.exe $(_ZVcpkgAppLocalPowerShellCommonArguments)"
	IgnoreExitCode="true"
	UseCommandProcessor="false">

Using WHERE command to check if pwsh.exe is in a specific %PATH% fixes this bug

• Changes comply with the maintainer guide.
• SHA512s are updated for each updated download.
• The "supports" clause reflects platforms that may be fixed by this new version.
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[BillyONeal]

I don't believe the output is 'incorrect'. I believe the correct fix is to deploy z-applocal and get rid of the powershell dependency completely. I asked Victor to see if our metrics can tell us whether enough folks are trying that option yet.

If the answer is 'not enough folks are using that yet' we should consider asking anyone complaining about this to enable that instead.

[berryzplus]

Sorry for the inconvenience. It seems better to set this to false.

Suggested change

	UseCommandProcessor="true">
	UseCommandProcessor="false">

[berryzplus]

@BillyONeal

I don't believe the output is 'incorrect'. I believe the correct fix is to deploy z-applocal and get rid of the powershell dependency completely. I asked Victor to see if our metrics can tell us whether enough folks are trying that option yet.

If the attached comment, "Search %PATH% for pwsh.exe if it is available." is correct, then I think the command is wrong.

As you know, vcpkg.exe downloads the latest pwsh.exe at runtime.
It is necessary to investigate why the Exec task tries to search the installed pwsh.exe instead of the downloaded one.

In my scenario, pwsh.exe is not involved, so I don't want to see "unrecognized command" errors.