E2E Deployment Test Failure: Aspire.Deployment.EndToEnd.Tests.FrontDoorDeploymentTests.DeployReactTemplateWithFrontDoor

## Failing Test

`Aspire.Deployment.EndToEnd.Tests.FrontDoorDeploymentTests.DeployReactTemplateWithFrontDoor`

## Workflow Run

[Deployment E2E Tests — 2026-06-08 (run 27116191858)](https://github.com/microsoft/aspire/actions/runs/27116191858/job/80024042009)

## Symptom

The pipeline reports `20/22 steps succeeded` but `provision-server-containerapp` fails with:

```
04:49:58 (pipeline-execution) ✗ [ERR] Deployment failed: Error code = ContainerAppOperationError,
Message = Failed to provision revision for container app 'server'. Error details:
The following field(s) are either invalid or missing.
Field 'template.containers.server.image' is invalid with details:
'Invalid value: "acaacral44rw5fzb4ui.azurecr.io/server:aspire-deploy-20260608044252":
Get "https://acaacral44rw5fzb4ui.azurecr.io/v2/": dial tcp: lookup
acaacral44rw5fzb4ui.azurecr.io on 100.100.248.28:53: no such host';..
```

The `WaitUntilText("Pipeline succeeded")` step then times out after 30 minutes.

## Root Cause

The ACA control plane validates `template.containers..image` by performing a live DNS lookup of the registry hostname. When `aspire deploy` provisions a fresh Azure Container Registry and then immediately provisions container apps that reference images in that registry, the ACA validator can hit ACA-side DNS resolvers before the new `.azurecr.io` record has propagated, producing `no such host`.

This is the same DNS-propagation race tracked in #17739 (`AzureStorageDeploymentTests.DeployStarterWithSharedAzureStorageReferences`).

## Notes

- `provision-aca` and `provision-frontdoor` succeed; only the container-app provisioning steps that reference the freshly created ACR fail.
- Likely transient / infrastructure-side; would benefit from a retry or readiness probe on the registry hostname inside the ACA provisioning step.
- Auto-filed by the deployment-test analysis workflow.