Refactor ZIP extraction for PowerShell compatibility

[showbiz2k]

Description

Powershell core Expand-Archive cmdlet does not define the -DestinationPath parameter causing a failure to unpack. Powershell core uses -OutputPath instead.

Checklist

• Is this feature complete?
  • [X ] Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • [X ] 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
  • [ X] 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
  • [ X] No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire.dev issue:
      • New issue
  • [X ] 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 -- 15692

Or

• Run remotely in PowerShell:

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

[Copilot]

Pull request overview

Updates the Aspire CLI installer PowerShell script to handle ZIP extraction across Windows PowerShell vs PowerShell (Core), aiming to fix a parameter incompatibility when calling Expand-Archive.

Changes:

• Routes ZIP extraction through Invoke-WithPowerShellVersion to call different Expand-Archive parameter names for modern vs legacy PowerShell.

[Copilot]

The ModernAction uses Expand-Archive -OutputPath, but elsewhere in this script (e.g., extension extraction) Expand-Archive is invoked with -DestinationPath under $Script:IsModernPowerShell. This inconsistency strongly suggests -OutputPath is not a valid parameter for the Expand-Archive available in pwsh, and will cause Windows installs under PowerShell Core to fail. Prefer keeping -DestinationPath for both branches, or (more robustly) select the parameter name by checking Get-Command Expand-Archive.Parameters for DestinationPath vs OutputPath.

Suggested change

	Expand-Archive -Path $ArchiveFile -OutputPath $DestinationPath -Force -ErrorAction Stop
	Expand-Archive -Path $ArchiveFile -DestinationPath $DestinationPath -Force -ErrorAction Stop