resErGatewayLock is improperly scoped on resVpnGateway

[DavidLHannah]

What happened? Provide a clear and concise description of the bug, including deployment details.

When you use the parExpressRouteGatewayLock to enable a resource lock on the resErGateway resoucre, the lock resErGatewayLock is in fact created on the resVpnGateway resource.

Please provide the correlation id associated with your error or bug.

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

What was the expected outcome?

When you use the parExpressRouteGatewayLock to enable a resource lock on the resErGateway resource, the lock resErGatewayLock should be created scoped to the resErGateway resource

Relevant log output

No response

Check previous GitHub issues

• I have searched the issues for this item and found no duplicate

Code of Conduct

• I agree to follow this project's Code of Conduct

[oZakari]

Great catch, @DavidLHannah, and thank you for your PR as well!