Add ability to specify Windows App SDK version in C# dotnet and VSIX templates

[lauren-ciha]

Extends #6407 and resolves #6343

In previous PRs, the UseLatestWindowsAppSDK was used in the dotnet templates to update the template project dependencies to the latest version. However, if this option was unchecked or set to false, no dependencies would be installed at all. This PR fixes this error by setting the default dependency version to the latest version in the ProjectTemplate.csproj themselves with PackageReference and providing parameters to pass in specific NuGet package versions for each template's dependencies.

Before this PR, the VSIX templates installed their packages via the NuGetPackageInstaller wizard, even though C# projects have long had PackageReference support. The reason was to have one implementation to manage package installation for both C# and C++ templates. Now that the Windows App SDK templates extend beyond Visual Studio, it does not make sense for the C# templates to use the Wizard class when evergreen dependency versions can be written into the project files. Further work is needed to completely remove the wizard from the C# VSIX templates, however that is out of scope for this PR. Setting PackageReference... Version="*" simplifies the default NuGet dependency versioning for both dotnet and VSIX templates.

That only covers the default case. To accommodate custom versioning on template generation, I added {dependency}Version parameter for each of the template dependencies. When the parameter is empty, it is replaced with the latest version (*). Other templates have new parameters for their additional dependencies.

Walkthrough with the single-project/blank app template

To illustrate the changes, let's walk through the blank app/single-project packaged app template:

• dev/Templates/Source/ProjectTemplates/Desktop/CSharp/SingleProjectPackagedApp/ProjectTemplate.csproj no longer has the dotnet conditional because we want VSIX dependencies to be resolved with PackageReference as well.
  *dev/Templates/Source/ProjectTemplates/Desktop/CSharp/SingleProjectPackagedApp/WinUI.Desktop.Cs.SingleProjectPackagedApp.vstemplate sets those CustomParameter to *. This makes sense for the VSIX templates since we do not have the UI to select versions (outside of the scope of this PR)
• Then in dev/Templates/Dotnet/templates/blank-app/.template.config/template.json, UseLatestWindowsAppSDK has been removed and the default values for the other depdency versions have been replaced to the floating latest stable value (*). This will make the templates easier to maintain in the long run if we want the default value to be the highest stable available. Since the post-actions were updating to the latest version, they're no longer needed. If NuGet restore fails, there is a clear error to the user and since the dependencies have moved into the project file, we don't need to add another version on failure.
• dev/Templates/Dotnet/templates/blank-app/.template.config/ide.host.json and dev/Templates/Dotnet/templates/blank-app/.template.config/dotnetcli.host.json surface these parameters to the user in Visual Studio and donet CLI respectively

These changes have been made to each of the C# templates.

Finally, dev/Templates/Dotnet/Test-DotnetNewTemplates.ps1 was updated to include tests for the version parameter parsing:

• If a version parameter is left blank in the dotnet CLI, it's set to *
• If a real Windows App SDK version is passed in, the instantiated project has that version
• If multiple versions are pinned, those versions are set in the instantiated templates
• If a prerelease string is included in the version (e.g. preview), the version is set correctly
• If an invalid NuGet version was passed in, the parameter is passed to NuGet, but NuGet restore fails
• If a valid NuGet version was passed in, but was not a WASDK version, the parameter is passed to NuGet, but NuGet restore fails

Considered paths (and the current limitations):

• Command line/template level parameter validation would reduce the time it would take for someone to realize they made a typo. Unfortunately, parameter-level validation was not supported
• Hiding the several version input boxes in VS' New Project menu behind a checkbox so that users would not have to look at all their versioning options if they just wanted the default. Unfortunately, although the boolean isVisible can be set, the values are set at instantiation time (e.g. VS' "Create" button) and are not responsive to user input. This is a Visual Studio limitation.

How I validated this PR:

• Ran Test-DotnetNewTemplates.ps1 - passed
• Manually installed, opened, and built all of the dotnet tests in VS - passed
• Built and installed the vsix using build-install-localdev-vsix.ps1 and instantiated and built the templates in VS - passed
• Running the branch through the aggregator pipeline (user/laurenciha/default-highest-nuget-version-csharp-templates)

A microsoft employee must use /azp run to validate using the pipelines below.

WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.

For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.