[IGNORE] Running Cli E2E tests with 13.2

[radical]

• All install methods now use --install-path to install to temp directories
• Docker tests use /tmp/aspire-install (ephemeral container)
• Non-Docker tests use C#-generated unique paths via Guid
• rm -rf ~/.aspire before each install for clean environment
• Added SetupAspireCliFromPullRequestAsync/SetupAspireBundleFromPullRequestAsync composite helpers that handle install, PATH setup, and version verification
• InstallAspireCliVersionAsync now handles PATH setup internally
• Old individual Install/Source methods made private with installPath parameter
• Simplified callers in all 4 non-Docker test files

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

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/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 15414

Or

• Run remotely in PowerShell:

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

[github-actions]

Re-running the failed jobs in the CI workflow for this pull request because 1 job was identified as retry-safe transient failures in the CI run attempt.
GitHub was asked to rerun all failed jobs for that attempt, and the rerun is being tracked in the rerun attempt.
The job links below point to the failed attempt jobs that matched the retry-safe transient failure rules.

• Tests / Npgsql / Npgsql (windows-latest) - Failed step 'Set up job' matched the transient annotation allowlist.

[github-actions]

Re-running the failed jobs in the CI workflow for this pull request because 1 job was identified as retry-safe transient failures in the CI run attempt.
GitHub was asked to rerun all failed jobs for that attempt, and the rerun is being tracked in the rerun attempt.
The job links below point to the failed attempt jobs that matched the retry-safe transient failure rules.

• Tests / Npgsql.EntityFrameworkCore.PostgreSQL / Npgsql.EntityFrameworkCore.PostgreSQL (windows-latest) - Failed step 'Set up job' matched the transient annotation allowlist.