Suggestion: Name property validation

[WhitWaldo]

Is your feature request related to a problem? Please describe.
Azure has an awful lot of resources available to ARM and just about every one of them has a different convention for naming things, whether that be the min/max length of the name, whether it's case-sensitive or not, what characters can be used, etc.

Given that we've got Intellisense for building out each of the sections in Bicep, it'd be great to also get a visual hint of what's allowed with a build-in validator to help someone naming the resource while authoring their Bicep file.

Describe the solution you'd like
When setting the value of any "name" property, a tooltip should appear (not unlike the preview of required properties provided by scaffolding) that indicates clearly the various requirements around naming that type of resource. Additionally, as someone types, the value should be passed through regular expression validation to verify that the user is following the rules in real-time, so they don't deploy the project and are later surprised by the result.

Where possible, when using string concatenation or functions to build the names, it'd similarly be great if the string could be evaluated in advance to again check for validity (e.g. knowing that uniqueString() returns a 13-character string and verifying if it plus your other values exceeds the maximum length.

[alex-frankel]

This work is tracked in #1679. This information is already in the swagger specs for a lot of resource types, so we should be able to consume that info and validate against it. From there, we'll focus on making sure all the swagger specs have their naming restrictions specified if applicable.