Aspire CLI: new command arg forwarding

There's a lot of design decisions that need to be discussed as it relates to forwarding CLI arguments from `aspire new` to the `dotnet new`. For example, this command isn't supported:

```
aspire new aspire-starter -n AspireApp -o AspireApp --use-redis-cache
```

Nor is this command:

```
aspire new aspire-starter -n AspireApp -o AspireApp -- --use-redis-cache
```

One might assume that they could pass arguments that are known to be dotnet template args, but that's not the case. Should we prompt in the CLI for these values? Or should we just forward unmatched args to the underlying command?