Discover methods to pester test the use of hardcoded name prefix without conflicting with similar strings in the parameter file

Testing for the detection of hardcoded name prefix instead of a token, introduces the likelihood that a deployment will get blocked due to other conflicting strings in things that are not part of a prefix, but part of a parameter name:

For example, if the name prefix is set to `sub` and the parameter file contains the word `subscription` then detecting the word `sub` means that the parameter file invalid, but in fact it shouldn't be the case.