[Modules] Update private endpoint module reference to support location input and subnet location reference

[ahmadabdalla]

Description

Currently the nested private endpoint module in each resource has the hardcoded location that uses the reference function to capture the location from the subnet

location: reference(split(privateEndpoint.subnetResourceId, '/subnets/')[0], '2020-06-01', 'Full').location

While this is true where the private endpoint needs to be in the same location as the subnet. This requires any service principal / user deploying the module to have at least 'VNET Read' permissions.

In an environment where RBAC is assigned at the subnet level (i.e. shared VNET infra between different apps), this means that at least 2 RBAC roles are required for the user/service principal to be able to deploy a resource + private endpoint all together.

A workaround is to NOT use the PE feature in each module, but rather deploy the PE separately using the PE module where there is more control on that location

This PR addresses this issue by providing an option on the PE nested module to check if the user has passed the location property and use that, and then fall back to the existing implementation. This is backwards compatible with the existing implementation and supports the scenario where RBAC is done at the subnet level and not the VNET level.

location: contains(privateEndpoint, 'location') ? privateEndpoint.location : reference(split(privateEndpoint.subnetResourceId, '/subnets/')[0], '2020-06-01', 'Full').location

Pipeline references

Pipeline

Type of Change

• Bugfix (non-breaking change which fixes an issue)

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• My corresponding pipelines / checks run clean and green without any errors or warnings
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (readme)
• I did format my code