Add New CI Pipeline for Latest WindowsAppSDK

[shuaiyuanxx]

Summary

This PR introduces the following changes to the CI pipeline and version management:

Pipeline Enhancements:

• Added a new script UpdateVersions.ps1 to automate the update of Microsoft.WindowsAppSDK versions across various project files.
• Introduced a new pipeline configuration ci-using-the-latest-winappsdk.yml to build using the latest Microsoft.WindowsAppSDK.
• Updated existing pipeline configurations to support the new useLatestWinAppSDK parameter.

Pipeline Configuration Updates:

• Updated job-build-project.yml to handle the useLatestWinAppSDK parameter and adjust the RestoreAdditionalProjectSourcesArg accordingly.
• Added a new template steps-update-winappsdk-and-restore-nuget.yml for updating and restoring NuGet packages with the latest Microsoft.WindowsAppSDK.

PR Checklist

• Closes: #xxx
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated
• New binaries: Added on the required places
  • JSON for signing for new binaries
  • WXS for installer for new binaries and localization folder
  • YML for CI pipeline for new test projects
  • YML for signed pipeline
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Changes

New Files

• .pipelines/UpdateVersions.ps1: Script to update Microsoft.WindowsAppSDK versions.
• .pipelines/v2/ci-using-the-latest-winappsdk.yml: New pipeline configuration for using the latest Microsoft.WindowsAppSDK.
• .pipelines/v2/templates/steps-update-winappsdk-and-restore-nuget.yml: Template for updating and restoring NuGet packages.

Modified Files

• .pipelines/v2/templates/job-build-project.yml: Updated to handle useLatestWinAppSDK parameter and adjust MSBuild arguments.
• .pipelines/v2/templates/pipeline-ci-build.yml: Added useLatestWinAppSDK parameter.

Validation Steps Performed

• Verified that the new .pipelines/UpdateVersions.ps1 script correctly updates the Microsoft.WindowsAppSDK versions in the relevant project files.
• Ensured that the new pipeline configuration builds successfully with the latest Microsoft.WindowsAppSDK.
• Tested the conditional execution of verifyNoticeMdAgainstNugetPackages.ps1 based on the useLatestWinAppSDK parameter.

[crutkas]

I feel with this, maybe it is time to migrate the cpp projects also over to a centralized prop like we did with the c# stuff.

[crutkas]

this feels like it would change overtime, no?

[shuaiyuanxx]

The project and definition IDs in Azure Pipelines are unique identifiers for a specific project and pipeline definition, respectively. These IDs do not change over time unless you explicitly delete and recreate the project or pipeline, which would generate new IDs.

[crutkas]

is this just being safe in the future?

[shuaiyuanxx]

Just got the idea from the pipeline in WindowsAppSDK-Samples, it also did it in this way: https://github.com/microsoft/WindowsAppSDK-Samples/blob/main/UpdateVersions.ps1

[crutkas]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[shuaiyuanxx]

Doing some test for the code update, close it until the pipeline passed all the test.