Resolve 'Name' Ambiguity

[rudiv]

Bicep resources sometimes effectively have 2 "Name"s.

The first (which is Name in the internal API) is the actual Bicep Resource Name, ie.

          \/ This
resource test 'Test/test@2023-01-01' = {

The second, which almost has a convention of AccountName for the existing few resources is the actual name of the resource, example in Cosmos DB:

resource cosmosDbAccount 'Microsoft.DocumentDB/databaseAccounts@2023-11-15' = {
                              name: 'cosmos${uniqueString(resourceGroup().id)}'
                                        ^ This

To avoid the ambiguity of Name being used for both there are a couple of options neither of which I'm sure is really better than the other:

1. Remove the concept of the Resource Name as being customisable, so we would always "auto generate" a unique (but constant) string, which could be based off the "Account Name". This has the upside of removing any ambiguity as it becomes internal, but the downside of making Bicep (if synthed) more unreadable / usable outside of tooling.
2. Standardise Name as ResourceName that can be overridden and used internally, leaving Name to be used when required by the resource definition itself.

Either of those work to remove the less defined Name property used for Bicep and reduce confusion when implementing new resources.