windows-latest workflows now use Windows Server 2022

[KyleEvers]

Action Builds now fail because of how we are explicitly calling MSbuild and the change to Windows Server 2022 as windows-latest

Example Failure):

Run cd "C:\Program Files (x[8](https://github.com/KyleEvers/SharpCollection/runs/5139715487?check_suite_focus=true#step:5:8)6)\Microsoft Visual Studio\201[9](https://github.com/KyleEvers/SharpCollection/runs/5139715487?check_suite_focus=true#step:5:9)\Enterprise\MSBuild\Current\Bin\"
Set-Location: D:\a\_temp\9b8e3db1-a48a-4e19-94ab-ec8e504e20f0.ps1:2
Line |
   2 |  cd "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MS …
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Cannot find path 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\'
     | because it does not exist.

In the short term update cd command to new MSbuild directory. Long term be Visual Studio version agnostic and dynamically resolve MSbuild location.

[KyleEvers]

Resolved by commit 5ca2224

Per Github Action Windows 2022 Documentation the MSBuild location moved to C:\Program Files\Microsoft Visual Studio\2022\Enterprise