Add New CI Pipeline for Latest WindowsAppSDK

[shuaiyuanxx]

Summary

The old PR cannot be reopened, so I create a new PR

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.
• Added WinAPPSDK version selection, the pipeline can be manually triggered to use the specified version.

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]

FYI, you can mark it as draft until you're ready.

[shuaiyuanxx]

FYI, you can mark it as draft until you're ready.

Got it, it's ready for review now

[jaimecbernardo]

Hi, we've added the "Don't Merge" tag to the PR, since we're trying to keep the repo stable for the release and possible hotfix if necessary. Please don't merge the PR while the tag is still in here. This allows people to review the PR and approve with less fear that it'll get merged 😄

[yeelam-gordon]

Thanks for the change, overall looks good, have minor comments.

[yeelam-gordon]

Oh, with this, we can make it as single line then.
Since I see there is no security concern for "making up the build parameters", as the result, we can directly like WITHOUT IF ELSE
msbuildArgs: >-
/p:CIBuild=true;NoBuild=true -t:pack
/bl:$(LogOutputDirectory)\build-hosts.binlog
$(MSBuildArgs.UseVSPreview)
$(RestoreAdditionalProjectSourcesArg)

[yeelam-gordon]

Any reason to be string instead of boolean?

[shuaiyuanxx]

When the pipeline calls the PS1 file, the passed parameters are converted to string type.

[DHowett]

That is unexpected.

You can pass any type of PowerShell object to a script in a pipeline.

pwsh: |-
  & ./Path/To/Script.ps1 -BooleanArgunent $true

If you need to convert an azure DevOps yaml boolean into a PowerShell boolean, you can use...

$${{parameters.azureDevopsYamlBoolean}}

This will evaluate to $true or $false (the first $ is for PowerShell, and the second one is for Azure DevOps!)

[yeelam-gordon]

For these big chunk of code, would you mind to break it down into smaller functions?
As the result, the main one will looks cleaner

[yeelam-gordon]

e.g.
function Update-PackageConfig {
param (
[string]$filePath,
[string]$oldVersionString,
[string]$newVersionString
)
# Function implementation
}