internalLoadBalancingMode is not working as expected in ASE ILB V2 create template

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

Sorry to hear you had a bad experience with one of the templates :worried: But, in case you're just asking a question, we're happy to help. You can also check if the question might already have been asked here https://github.com/Azure/azure-quickstart-templates/issues?utf8=%E2%9C%93&q=is%3Aissue

We've created an outline of recommended sections to fill out that will help make this Pull Request awesome!

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

[Template Name goes here](Template link goes here)

### Issue Details
If we set “internalLoadBalancingMode” to 1, it is actually “2”(ftp only); and when we set it to 3, it is actually “0”(Public IP only);
Please relaunch west ASE in staging V2 as well.

Template metadata for internalLoadBalancingMode:
": "0 = public VIP only, 1 = only ports 80/443 are mapped to ILB VIP, 2 = only FTP ports are mapped to ILB VIP, 3 = both ports 80/443 and FTP ports are mapped to an ILB VIP."

### Repro steps (*if necessary, delete otherwise*)
1. launch the template into a private subnet, with internalLoadBalancingMode 3;
2. once launched, create a new web app in the ILB ASE;
3. the ftp site url is something like ftp://myasedomain.com;
4.when we query the ports on the VIP, 80, 443 and 21 are all blocked;
5. so it looks like option 3 is actually option 0;
6. we did another test and use internalLoadBalancingMode 1, but it actually acted like option 2(ftp only);

Start by locating the ASE ILB V2 create template referenced in the title and inspect how internalLoadBalancingMode is passed through. Reproduce the deployment with values 1 and 3, then verify that the resulting VIP exposes the documented ports: 80/443, FTP, or both as appropriate.

Written by the indexing model from the issue text.