Remove unnecessary Azure Load Balance from MC Resource Group

[jlester-msft]

Describe the bug
The current CoA deployment script creates a kubernettes load balancer with only a single backend pool and no associated NIC/IP configured. With this configuration the kubernettes load balancer isn't doing anything.

Steps to Reproduce

Expected behavior

Deployment details: (any information you can provide would be helpful):

Screenshots

Additional context
Upcoming Azure Tenant Baseline rules will start flagging unnecessary resources like this, so this should be fixed in future releases. I am assuming this load balancer is created by an unintended consequence of a configuration in the deployer.