Use staging feed for dotnet tool smoke tests

[radical]

Description

Updates CLI E2E dotnet tool staging installs so ASPIRE_E2E_QUALITY=staging resolves the staging install-script CLI first, derives the matching SHA-specific darc-pub-microsoft-aspire-* NuGet feed, and installs Aspire.Cli from that stable staging source instead of using the latest prerelease package.

This keeps dotnet tool smoke tests aligned with install-script staging builds such as 13.3.0+<sha> and prevents drift to a newer preview train.

Fixes # (issue)

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 -- 16655

Or

• Run remotely in PowerShell:

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

[radical]

Validation run for staging - https://github.com/microsoft/aspire/actions/runs/25228048774
Validation run for dev - https://github.com/microsoft/aspire/actions/runs/25228049843

[Copilot]

Pull request overview

This PR updates Aspire CLI E2E “dotnet tool” staging installs so that ASPIRE_E2E_QUALITY=staging resolves the staging install-script build first, derives the matching SHA-scoped darc-pub-microsoft-aspire-<sha8> feed, and installs Aspire.Cli from that staging feed (instead of drifting to the latest prerelease). It also adds an automated check in the daily smoke workflow to ensure all smoke routes installed the same CLI version.

Changes:

• Add a staging-specific dotnet tool install path that derives a SHA-specific staging NuGet feed from the staging CLI --version output.
• Add verify-daily-smoke-cli-versions.ps1 + infrastructure tests to validate version-record consistency and report failures via step summary.
• Update the daily smoke GitHub Actions workflow to run the version-consistency verification step after tests.

Reviewed changes

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

Show a summary per file

File	Description
tests/Shared/CliInstallStrategy.cs	Adds UsesStagingDotnetToolFeed and generates a staging-feed-aware dotnet tool install command for Docker scenarios.
tests/Infrastructure.Tests/PowerShellScripts/VerifyDailySmokeCliVersionsTests.cs	Adds coverage for the new PowerShell verification script (success + multiple failure modes).
tests/Infrastructure.Tests/Infrastructure.Tests.csproj	Links MSBuildUtils so Infrastructure.Tests can locate repo-root scripts.
tests/Aspire.Cli.EndToEnd.Tests/SmokeTests.cs	Adjusts TypeScript AppHost config assertions to vary expected channel based on install quality (note: currently inconsistent with the invoked --channel stable).
tests/Aspire.Cli.EndToEnd.Tests/Helpers/CliInstallStrategyTests.cs	Updates expectations for staging dotnet tool behavior and adds coverage for the new staging install command.
eng/scripts/verify-daily-smoke-cli-versions.ps1	New script to ensure all daily smoke install routes used the same Aspire CLI version and optionally write a step summary on failure.
.github/workflows/tests-daily-smoke.yml	Runs the new version-consistency script after smoke tests complete.

[radical]

Closing in favor of #17532 .