[BUG] Azure AKS Automatic SKU provisions a Public IP with Private Clusters

**Describe the bug**
Creating an AKS Automatic SKU provisions a Standard Load Balancer with a Public IP Address, even with a Private Cluster and an Outbound Type of userDefinedRouting

When usuing a Base SKU, only private IPs are provisioned

**To Reproduce**
Steps to reproduce the behavior:

1. Run command

```
az aks create --resource-group "aks-auto" --name "aks-auto" --location "westeurope" `
--apiserver-subnet-id "/subscriptions/xxxx/resourceGroups/infra/providers/Microsoft.Network/virtualNetworks/infra-vnet/subnets/aks-auto-api" `
--vnet-subnet-id "/subscriptions/xxxx/resourceGroups/infra/providers/Microsoft.Network/virtualNetworks/infra-vnet/subnets/aks-auto-sub" `
--assign-identity "/subscriptions/xxxx/resourcegroups/aks-auto/providers/Microsoft.ManagedIdentity/userAssignedIdentities/aks-auto-sam" --enable-apiserver-vnet-integration --sku automatic --enable-private-cluster --no-ssh-key --outbound-type userDefinedRouting
```
2. See Issue
A Standard Load Balancer with a Public IP is created in the MC Managed Resource Group

**Expected behavior**
No Public IP addresses created (like --sku base)

**Screenshots**

**Environment**

- CLI Version [2.85.0]
- Kubernetes version [1.34.7]