Linter should catch resource naming convention

Azure Cloud Adoption Framework best practices define a naming convention, which recommends a resource type prefix. Linter should check the naming convention for resources, such as the resource type prefix.

https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming

Currently, the resource type prefix is not widespread. Most Azure Quickstart Templates, let alone the Azure portal, don't use a resource type prefix. Linter helps end the mess.

No files, tests, or entry points are named. Start by reviewing the Azure Cloud Adoption Framework resource-naming guidance linked in the issue and the existing linter behavior, then define which resource prefixes are supported and how naming violations should be reported. Done means the linter consistently checks the agreed convention without incorrectly flagging existing valid templates.

Written by the indexing model from the issue text.