Command Input inconsistency between Dashboard & CLI

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

I just upgraded https://github.com/afscrome/aspire-dotnet-jwts to use command inputs in 13.4

If I have a command with an input the that a default value, the dashboard will prompt me to pick a value

But if I run this same thing via the CLI, then there is no prompt.

```
> aspire resource apiservice jwt-user
✅ Command 'jwt-user' executed successfully on resource 'apiservice'.
eyJhbGciOiJIUzI1NiIsImtpZCI6InNpZ25pbmcta2V5IiwidHlwIjoiSldUIn0.eyJpc3MiOiJUZXN0LUp3dC1zaWduaW5nLWtleSIsImV4cCI6MTc4MTg5NTg3NiwibmJmIjoxNzgxODkyMjc2LCJhdWQiOiJkb3RuZXRhcHB3aXRoYXV0aCIsInN1YiI6ImRldi11c2VyIiwiYWdlIjoiMTgiLCJpYXQiOjE3ODE4OTIyNzZ9.Iy8Ys2bjcfWJYMwHHVuDdxcC2suPXeyycRYM6L4LIC0
```

### Expected Behavior

I'd expect the two to behave similarly. (With the exception of the CLI falling back to the default without prompting if `--non-interactive` is provided).

### Steps To Reproduce

https://github.com/afscrome/aspire-dotnet-jwts/commit/d2b592ab1fd4818a8bd53f62181b67951b7e8feb

### Exceptions (if any)

_No response_

### Aspire doctor output

```
Aspire Environment Check
========================

Aspire
✅ Aspire CLI version 13.4.5 (channel: stable)

AppHost
✅ AppHost version 13.4.5 (playground/AppHost/aspirifriday.AppHost.csproj)

.NET SDK
✅ .NET 10.0.301 installed (arm64)

Container Runtime
⚠️ Docker: installed but not running ← active
Start Docker Desktop

Environment
✅ HTTPS development certificate is trusted
⚠️ HTTPS development certificate has an older version (v5)
Run 'aspire certs clean' to remove all certificates, then run 'aspire certs trust' to create and trust a new
one.
See: https://aka.ms/aspire-prerequisites#dev-certs
Details:
Older certificate versions (< v4) may not support all certificate trust scenarios.

Summary: 4 passed, 2 warnings, 0 failed
For detailed prerequisites: https://aka.ms/aspire-prerequisites

Aspire CLI Installations
========================

╭──────────────────────────────────────────┬──────────────────────────────────────────┬─────────┬───────────┬─────────────╮
│ Path │ Version │ Channel │ Route │ PATH status │
├──────────────────────────────────────────┼──────────────────────────────────────────┼─────────┼───────────┼─────────────┤
│ /Users/alex/.aspire/bin/aspire (current) │ 13.4.5+73114e86c64aeb9f3f3c7da8e37df1ae4 │ stable │ (unknown) │ active │
│ │ 281b27e │ │ │ │
╰──────────────────────────────────────────┴──────────────────────────────────────────┴─────────┴───────────┴─────────────╯

```

### Anything else?

_No response_

Reproduce the issue using the linked aspire-dotnet-jwts commit, then compare the dashboard command-input flow with `aspire resource apiservice jwt-user`. Trace how default-valued inputs are handled in each interface, including the `--non-interactive` case; done means interactive CLI execution prompts like the dashboard and non-interactive execution uses the default.

Written by the indexing model from the issue text.