Stage native CLI tool packages deterministically

[radical]

Description

Adds deterministic staging for native Aspire CLI tool packages in the Azure DevOps publishing pipeline.

The pipeline now calls a shared PowerShell script that stages exactly one canonical Aspire.Cli pointer package and one RID-specific package per native archive artifact, while failing fast on missing pointer packages, RID/package mismatches, duplicate RID packages, and version mismatches. Both official and unofficial Azure DevOps pipeline definitions use the same script.

Validation:

• ./restore.sh
• ./build.sh --build /p:SkipNativeBuild=true
• dotnet test --project tests/Infrastructure.Tests/Infrastructure.Tests.csproj --no-build --no-launch-profile -- --filter-class "*.StageNativeCliToolPackagesTests" --filter-not-trait "quarantined=true" --filter-not-trait "outerloop=true"

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire.dev issue:
      • New issue
  • No

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 16631

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 16631"

[radical]

Validating this PR with the internal AzDO pipeline: https://dev.azure.com/dnceng/internal/_build/results?buildId=2964700

[Copilot]

Pull request overview

This PR makes native Aspire CLI tool package staging deterministic in the Azure DevOps publishing pipeline by centralizing staging logic in a shared PowerShell script and adding infrastructure tests to validate expected behaviors and failure modes.

Changes:

• Added eng/scripts/stage-native-cli-tool-packages.ps1 to stage exactly one canonical Aspire.Cli pointer package plus one RID-specific package per native-archive RID, with validation for duplicates/mismatches.
• Updated both official and unofficial Azure DevOps pipelines to invoke the shared staging script instead of inlining staging logic.
• Added Infrastructure.Tests coverage for the staging script across success and multiple error scenarios.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
tests/Infrastructure.Tests/PowerShellScripts/StageNativeCliToolPackagesTests.cs	Adds test coverage for the staging script’s success path and fail-fast validations.
eng/scripts/stage-native-cli-tool-packages.ps1	Implements deterministic package discovery/validation and staging into the Shipping directory.
eng/pipelines/azure-pipelines.yml	Switches official pipeline staging step to call the shared script.
eng/pipelines/azure-pipelines-unofficial.yml	Switches unofficial pipeline staging step to call the shared script.

[radical]

Updated internal AzDO validation after addressing review feedback: https://dev.azure.com/dnceng/internal/_build/results?buildId=2964869