Delimiters Should Allow More Than One to Be Enabled and Have Order of Preference

**Tool version**
4.3.2

**Is your feature request related to a problem? Please describe.**
Certain Azure resource types only allow specific delimiters. When dash is selected as the default delimiter and one of those resource types are encountered, all delimiters are removed from the generated name.

**Describe the solution you'd like**
Allowing multiple delimiters to be enabled and a preference order to be specified would allow the system to generate a name that complies with the naming rules without needing to remove all delimiters unless none matched.

**Describe alternatives you've considered**
As a workaround, it's possible to temporarily change the selected delimiter to one that is allowed for the resource type and then change it back. This is not ideal as it requires an admin to make the change and then revert it once the name has been generated.

**Additional context**
This can specifically be seen with the osdisk resource type where generation with dashes results in all delimiters being removed and switching to underscore produces a name with the delimiters preserved.