Bug: `aspire deploy` Azure resource group selection

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

Today, when you call `aspire deploy` with an Azure subscription that already contains resource groups, you're prompted to either select and existing resource group or type to enter a new resource group. The bug is that you can only ever select an existing one - regardless of whatever you type, it's ignored and the currently selected resource group name in the CLI output is used.

### Expected Behavior

It should use the manually entered resource group name, when it's available.

### Steps To Reproduce

1. Create a new Aspire app from a template (the template doesn't matter)
2. Add an Azure hosting/deployment integration (Azure App Service or Azure App Containers)
3. Ensure you're logged into Azure with `az login` and that your sub has multiple resource groups.
4. Enter a name for a new resource group to be created and press enter.

It uses one from the list, not the newly entered resource group name

### Exceptions (if any)

_No response_

### .NET Version info

_No response_

### Anything else?

_No response_

Start with the `aspire deploy` resource-group prompt flow and reproduce it after `az login` with an Azure subscription containing multiple resource groups. Done means the manually entered resource-group name is used instead of the currently selected existing group; no file or test is named in the issue.

Written by the indexing model from the issue text.