Guiding customers to modern defaults

As services develop and evolve, they gather various switches to enable the "modern" behavior.

For example:

```bicep
resource workerFunctionSite 'Microsoft.Web/sites@2021-01-15' = {
kind: 'functionapp'
}
```

or

```bicep
resource storageacc 'Microsoft.Storage/storageAccounts@2021-04-01' = {
kind: 'StorageV2'
}
```

Portal can automatically default these switches to their latest value or hide them in some other way. These create an extra barrier for entry for customers getting started with IaC as they need to discover correct values and carry them forever.

One possible solution to this is analyzers that would point to modern defaults, another, pointed out by @anthony-c-martin, is a module registry where defaults would be encapsulated in modules.

The issue names no files, tests, or entry points. Start by clarifying whether the intended direction is analyzers or a module registry, then identify the relevant Bicep design areas; done requires an agreed approach and explicit behavior for guiding users toward modern defaults.

Written by the indexing model from the issue text.