Deployment test: FrontDoorDeploymentTests times out waiting for '(based on NuGet.config)' prompt

[mitchdenny]

Test

Aspire.Deployment.EndToEnd.Tests.FrontDoorDeploymentTests.DeployReactTemplateWithFrontDoor

Symptom

Hex1b automation times out after 60s waiting for the text (based on NuGet.config) to appear in the terminal after aspire add Aspire.Hosting.Azure.AppContainers.

Failure trace:

Xunit.MicrosoftTestingPlatform.XunitException: Hex1b.Automation.Hex1bAutomationException : Step 36 of 36 failed — WaitUntilText("(based on NuGet.config)")
  Timed out after 00:01:00 waiting for: text "(based on NuGet.config)" to appear

Root cause analysis

The test in FrontDoorDeploymentTests.cs:101 expects the package-source disambiguation prompt (PackagingStrings.BasedOnNuGetConfig) when running aspire add. The CLI now writes a NuGet.config with explicit Aspire* package source mappings, so the prompt no longer appears for these flows and the wait blocks forever.

Terminal snapshot at failure shows the add completed cleanly without the prompt:

[5 OK] $ aspire add Aspire.Hosting.Azure.AppContainers
📦 Created or updated NuGet.config in the project directory with required package sources.
✅ The package Aspire.Hosting.Azure.AppContainers::13.4.0-dev was added successfully.
[6 OK] $

Reproduction

• Scheduled Deployment Tests runs on main: consistently failing on the last 5 nightly runs (#26323258106, #26268417397, #26205530633, #26141293553, #26076159680).
• Also reproduced on PR Fix WithIngressClass parameter resolution for Kubernetes publish #17423 deployment-test run #26348648275 (unrelated to PR change).

Suggested fix

Either drop the WaitUntilTextAsync("(based on NuGet.config)") calls in FrontDoorDeploymentTests (lines 99-103 and 111-115) since they guard a prompt that no longer appears, or replace them with a polled wait that succeeds when either the prompt or the success line is observed.

Priority

High — blocks the FrontDoor E2E coverage on every scheduled Deployment Tests run.

/cc @mitchdenny