Fix deployment E2E nightly failures

[ideepakchauhan7]

Summary

This addresses the deployment E2E failures reported in #16057 from the April 11, 2026 nightly run.

The failing tests were all relying on outdated CI interaction assumptions:

• Python deployment tests were sourcing only the CLI binary in CI instead of the full Aspire bundle required by Python apphost flows.
• The TypeScript VNet SQL infra test still waited for a NuGet prompt that bundle-based installs no longer show.
• The compact naming upgrade test now needs to dismiss the template-version prompt before continuing.
• The managed Redis test matched the old output-path prompt text too strictly.

What Changed

• Switched the Python deployment CI setup paths to install/source the full Aspire bundle when running in CI.
• Updated the ACR purge task test so PR bundle installs do not re-handle the NuGet version prompt incorrectly.
• Removed the obsolete prompt wait from the TypeScript VNet SQL infra test.
• Updated the GA init flow in the compact naming upgrade test for the current CLI prompt sequence.
• Relaxed the managed Redis prompt matcher to handle the updated CLI text.

Impact

These changes align the deployment E2E tests with the current CLI and bundle behavior so the nightly deployment workflow can complete without the false failures seen in #16057.

Fixes #16057

Validation

• git diff --check
• Verified the six touched files match the existing upstream fix commit dd13e4cd041768a6e33ca51fa229ad660c1a8fd8
• Local dotnet build/test could not be run in this workspace because the .NET SDK is not installed here

[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 -- 16071

Or

• Run remotely in PowerShell:

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