Scaling up a compute machineset will fail in AzureStack UPI with:
```
Message: failed to create vm $clusterID-worker-mtcazs-2gjsl: failure sending request for machine $clusterID-worker-mtcazs-2gjsl: cannot create vm: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=404 -- Original Error: Code="NotFound" Message="The Availability Set '/subscriptions/$subID/resourceGroups/$clusterID-rg/providers/Microsoft.Compute/availabilitySets/$clusterID-cluster' cannot be found."
```
because machinesets follow the IPI pattern of using "$clusterID-cluster"
as the availabilitySet's name, whereas UPI uses "$clusterID-avset". So
let's change UPI to be consistent with IPI.
Another inconsistence is the RHCOS image name: UPI appends "-image" to
the name whereas IPI just uses the "$clusterID".
Switches the name of the internal load balancer to be
${INFRA_ID}-internal which is consistent with IPI.
Also renames the backend address pool to be the same as the
LB which is consistent with the public LB.
In the current solution, ASH only has one public load balancer. Both
api DNS records point to the public IP address. This creates an
internal load balancer and updates the docs to point the api-int
record to the internal LB.
Create the initial ARM templates for an Azure Stack Hub UPI cluster.
Co-authored-by: John Hixson <jhixson@redhat.com>
Co-authored-by: Patrick Dillon <padillon@redhat.com>
