201-web-app-ase-ilb-configure-default-ssl places certificate in the wrong place

201-web-app-ase-ilb-configure-default-ssl (https://github.com/Azure/azure-quickstart-templates/tree/master/201-web-app-ase-ilb-configure-default-ssl)

### Issue Details

We are using this template to deploy an ASE v2 with an SSL certificate. However, if we run this template, the certificate ends up as a private certificate in the web app that’s associated with the ASP in the ASE. There is no ILB certificate in the ASE.

This does not seem to be correct.

And as extra info on this:

We compared this ASE with another ASE where we attached the ILB certificated through the portal in resources.azure.com and noticed an extra ‘point’ was added in front of the certificate thumbprint in the clustersettings.value of the hostingenvironment for the certificate we added through the ARM template.

### Repro steps (*if necessary, delete otherwise*)
1. Create an ILB ASE through the portal. You can follow the steps here https://docs.microsoft.com/en-us/azure/app-service/environment/create-ilb-ase
2. Create a certificate and put is on blob storage (steps https://docs.microsoft.com/en-us/azure/app-service/environment/create-ilb-ase#post-ilb-ase-creation-validation, but don't do the actual upload)
3. Use the parameters from the ASE and certificate as input for this ARM template.
4. Check the location of the certificate, the certificate is now a private certificate in the app on the ASP in the ASE, but not on the ASE itself.

Open the 201-web-app-ase-ilb-configure-default-ssl template and inspect how its certificate and ASE resources are configured. Reproduce the deployment using the listed portal and blob-storage steps, then compare the deployed certificate location and clustersettings value with a portal-configured ILB certificate. Done means the certificate is attached to the ASE ILB rather than exposed as a private certificate in the app.

Written by the indexing model from the issue text.