Support further restricting resource/endpoint naming from hosting integrations

There are times when the current rules for what chars are allowed in resource names is not restrictive enough, e.g. for hypens/dahses (#13047).

We should consider adding support for hosting integrations to further restrict the resource naming scheme. This would be enforced at runtime and via the analyzer. The analyzer requires the information about the restriction to be available at build time so making the extensibility point here an MSBuild property or item type that hosting integration packages can set via custom build targets, e.g. `$(AspireResourceNameExtraDisallowedChars);-`.