Help please still not super thrilled with the lack of parity to the AZD and portal experiences. Neither of those even allow the customer to name the aspire dashboard dotnet component.

[MoazzemHossain-bot]

          still not super thrilled with the lack of parity to the AZD and portal experiences. Neither of those even allow the customer to name the aspire dashboard dotnet component. 

Could we maybe just add a default name of aspire-dashboard if the customer tries to create an dotnet component of type aspire dashboard but doesn't supply a name?

so command is a little more like a flag on the environment containerapp env dotnet-component create --environment my-env -g my-rg

rather than containerapp env dotnet-component create --environment my-env -g my-rg -n aspire-dashboard

Originally posted by @pauld-msft in https://github.com/Azure/azure-cli-extensions/pull/7564#discussion_r1596702671

### Tasks
- [ ] https://github.com/Azure/azure-cli-extensions/pull/7564

[yonzhan]

Thank you for opening this issue, we will look into it.