[AspireE2E]Aspire Dashboard: `aspire-managed.exe` remains running after dashboard shutdown causing "configured port is already in use" on next launch

**REGRESSION INFO:** Not a regression

**INSTALL STEPS**
1. Clean machine: Windows11 25h2 x64
2. Install [Node.js](https://nodejs.org/en)
3. Install Aspire CLI 13.4 : `npm install -g @microsoft/aspire-cli`

**REPRO STEPS**
1. Open CMD, run following commands:
```
aspire dashboard run
```
2. Ctrl +C to stop process
3. Run ` aspire dashboard run` again

**ACTUAL**
Dashboard could not start because a configured port is already in use. `aspire-managed.exe` remains running after CLI exit

**Note:**
1. The `aspire-managed.exe` process always running after stop the process

1. After end the task manually, ` aspire dashboard run` will work
2. This issue does not reproduces on `aspire run` in project folder.
3. This issue repros on `npm install Aspire CLI` not repro with ` iex "& { $(irm https://aspire.dev/install.ps1) }"` installed

**CLI Log**:

[aspire_Cli.txt](https://github.com/user-attachments/files/29998244/aspire_Cli.txt)

**EXPECTED**
Stopping the dashboard should terminate aspire-managed.exe and release all dashboard ports

Start by reproducing `aspire dashboard run` on Windows and review the attached CLI log while stopping it with Ctrl+C. Trace how the npm-installed CLI shuts down `aspire-managed.exe`; done means the process exits and the dashboard ports are released so a second `aspire dashboard run` succeeds without manual task termination.

Written by the indexing model from the issue text.