[AspireE2E] When the local deployment state has been deleted, execute `aspire destroy` should failed with clear message explaining destroy cannot proceed

**REGRESSION INFO:** New feature on Aspire 13.3

**INSTALL STEPS**
1. Clean machine: Windows11 25h2 x64
2. Install 10.0.202 SDK
3. Install Aspire CLI 13.3 : `iex "& { $(irm https://aspire.dev/install.ps1) } -Quality dev"`

**REPRO STEPS**
1. Open CMD, create an Aspire ASP.NET Core/Blazor Starter App using following commands:

`aspire new aspire-starter -n Aspire1`

1. Clear local deployment state
1. Run `aspire destroy`

**ACTUAL**
`aspire destroy` will execute successfully.

**EXPECTED**
It should execute failed with clear message explaining destroy cannot proceed

Start by reproducing the issue with the documented Aspire starter-app commands, clear the local deployment state, and run `aspire destroy`. Then trace the CLI's destroy command and its existing tests or error handling. Done means the command refuses to proceed when state is missing and reports clearly why destruction cannot continue.

Written by the indexing model from the issue text.