Consider defaulting required 'location' to 'resourceGroup().location'

In a lot of simpler deployment scenarios, customers would want to deploy resource groups and all the resources to be in the same location. It also creates friction for new customers that need to figure out why each resource needs to have its own location and what to set it to.

# Proposal

Default the required 'location' property of resources to 'resourceGroup().location'

# Before

```bicep
resource singleResource 'Microsoft.Storage/storageAccounts@2019-06-01' = {
name: '${name}single-resource-name'
location: resourceGroup().location
}
```

# After

```bicep
resource singleResource 'Microsoft.Storage/storageAccounts@2019-06-01' = {
name: '${name}single-resource-name'
}
```

# Analyzer

We can also add an analyzer that prompts users to remove the redundant qualification.

Happy to do the work if you decide this feature is something you are interested in.

Start with the issue's Before and After Bicep examples and the analyzer proposal. Identify the existing entry points for required resource properties and analyzer diagnostics, then verify that omitting location defaults to resourceGroup().location while redundant explicit qualifications receive a prompt.

Written by the indexing model from the issue text.