ResourceGroup should be at the service level and root of azure.yaml

[KSchlobohm]

Opening this issue as part of a feature request. My goal is to develop an azd template that is capable of deploying a multiregional web app. The tricky part of this goal seems to be adding support for multiple environments (e.g. dev, qa, prod) and asking for different behaviors per environment.

1. For non-prod environments my goal is to choose cheaper SKU like 'B1' for Azure App Service Plan. For a prod environment my goal is to choose a more powerful sku like 'P2V1'.
2. For non-prod environments my goal is to deploy to a single region. For a prod environment my goal is to deploy to multiple regions.

Having the ability to associate a service with a resource group would help me be more descriptive about the behavior I want to describe in the azure.yaml

[rajeshkamal5050]

@ellismg please take a look at it. Could be some additional requirements to your new environment proposal in Azd.

[jongio]

I would like to see resourceGroup at the root level and add it at the service level.

1. If at root, then all services should be deployed to that resource group
2. If at service, then that service is in that resource group
3. Otherwise, use our current defaulting logic.

This allows flexibility so a user can have services in any resource group.

[jongio]

I ran into this today where I have two services that need to be deployed to two different resource groups.

Can we add "resourceGroup" to services?