Ability to custom configure certain resource types

**Tool version**
Current version of the Azure Naming Tool you are running.
4.3.0
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I recently came across this tool, and it works great. However, we follow specific naming conventions for resource groups and global resources.

For sub-resource level resources, we use a suffix for the resource type, following the pattern:
project-application-environment-resource-type-location-instance-count

For resource-level items like resource groups, we follow a different convention:
resource-type-project-env-location (e.g., RG-POC-Dev-USC).

Since we distinguish resource-level naming from application-level naming, I haven't found a way to configure the tool to enforce these conventions separately. Is there a way to achieve this without spinning up an entirely new instance?
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
If there is any certain exclusion naming policy to be added to the resource type level, will be great
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
A different instance for the Global level naming convention, but it won't make sense, if any organisation follows some certain policies to some specific resources.
**Additional context**
Add any other context or screenshots about the feature request here.