[feature request] Add linter rule to require resources to include name pattern

[ArcturusZhang]

Clear and concise description of the problem

All resources should have a name constraint. Azure portal will always implement such a name constraint for resources, therefore such information should be documented in our typespec (and then it will show up in the swagger as well) and this will benefit every one.

Our CDK packages are heavily relying on name constraints for resources, it has been a nightmare that majority of our typespec does not really have one.

If we add a linter rule, at least for new resources, the service team will get noticed to write their name constraint on the resource.

Checklist

• Follow our Code of Conduct
• Check that this issue is about the Azure libraries for typespec. For feature request in the typespec language or core libraries file it in the TypeSpec repo
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[ArcturusZhang]

@lmazuel @markcowl what do you think about this?

[markcowl]

We already have such a rule: https://github.com/Azure/typespec-azure/blob/main/packages/typespec-azure-resource-manager/src/rules/arm-resource-name-pattern.ts

Are you seeing cases where this rule has been suppressed or isn't catching some instances?