Fix linter warnings in bicep templates

[jftl6y]

Several bicep templates are throwing linter warnings during compile. The most common is something like:
The name of variable 'builtInRoleNames_var' appears to have originated from a naming conflict during a decompilation from JSON. Consider renaming it and removing the suffix (using the editor's rename functionality). [https://aka.ms/bicep/linter/decompiler-cleanup]

Other warnings:

• Flagging potential security warnings for passwords or other secure values which do not include the @secure() attribute on parameters.
• Warning use-resource-id-functions: If property "policyDefinitionId" represents a resource ID, it must use a symbolic resource reference, be a parameter or start with one of these functions: extensionResourceId, guid, if, reference, resourceId, subscription, subscriptionResourceId, tenantResourceId. Found nonconforming expression at policyDefinitionId -> policyScopedId [https://aka.ms/bicep/linter/use-resource-id-functions]
• Warning no-hardcoded-location: Parameter 'location' may be used as a resource location in the module and should not be assigned a hard-coded string or variable value. Please use a parameter value, an expression, or the string 'global'. Found: '' [https://aka.ms/bicep/linter/no-hardcoded-location]

Describe the solution you'd like
Address all linter warnings.

[jrspinella]

Based on what I am doing with the testing fx, I had to fix the linter warnings to validate the modules. Once I merge my changes for this, linter warnings should be gone.

[OutKa5t]

Making this part of the PR process should reduce any further increase in warnings if it becomes an issue.