[BUG] MSBuild location defaults to VS2019 when VS2022 is installed

Project
Azure DevOps MSIX Packaging extension

Describe the bug
When both VS2019 and VS2022 are installed the pipeline task will default to using the VS2019 directory for MSBuild with no way of changing it.

To Reproduce
Install both Visual Studio 2019 and Visual Studio 2022 on an agent, run the MsixPackaging@1 task with msbuildVersion set to 'latest'.

Expected behavior
I expect the MSBuild of VS2022 to be used, located at: C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin\msbuild.exe
However the VS2019 version is being used, located at: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\msbuild.exe

Screenshots
If applicable, add screenshots to help explain your problem.

Platform
Windows Server 2016

Additional context
I know that I can set msbuildLocation but that feels like a poor solution to this issue, maybe an extra input can be added so users can set the version of Visual Studio they are using?

Start by tracing the MsixPackaging@1 task's handling of the msbuildVersion='latest' input and how it selects an installed Visual Studio directory. Reproduce the case with Visual Studio 2019 and 2022 installed, then verify that the task selects the VS2022 MSBuild path shown in the issue without requiring msbuildLocation.