E2E Deployment Test Failure: Aspire.Deployment.EndToEnd.Tests.TypeScriptAzureContainerAppJobDeploymentTests.DeployTypeScriptContainerAppJobsToAzureContainerApps

## Failing Test

`Aspire.Deployment.EndToEnd.Tests.TypeScriptAzureContainerAppJobDeploymentTests.DeployTypeScriptContainerAppJobsToAzureContainerApps`

## Symptom

The test reports `WaitUntil("success prompt [9 OK] $ (fail-fast on error)") — FAILED after 5:00.150`. The deploy step appears to succeed instantly with `4/4 steps succeeded • Total time: 94ms`, but the subsequent verification step fails with:

```
Resource group: e2e-ts-aca-jobs--1
Resource group not found
[ERR:1] $
```

## Root Cause

After `aspire init --language typescript --non-interactive`, the test writes its custom AppHost to **`apphost.ts`** in the workspace root:

https://github.com/microsoft/aspire/blob/main/tests/Aspire.Deployment.EndToEnd.Tests/TypeScriptAzureContainerAppJobDeploymentTests.cs#L120-L138

```csharp
File.WriteAllText(Path.Combine(workspace.WorkspaceRoot.FullName, "apphost.ts"), """ ... """);
```

Since PR #16984 ("Use mts for TypeScript AppHosts"), `aspire init --language typescript` creates an **`apphost.mts`** in the workspace root. The custom `apphost.ts` written by the test is never picked up by `aspire deploy`; it deploys the empty default `apphost.mts` instead, no resources are created in Azure, and the verification step fails because the resource group does not exist.

## Fix

Write the custom AppHost content to `apphost.mts` instead of `apphost.ts` (overwriting the empty init file).

## Affected Runs

- https://github.com/microsoft/aspire/actions/runs/26323258106 (2026-05-23)

> This issue was created automatically by a workflow analyzing Deployment E2E test failures on `main`.