Closed Issue: Defining HNSC under a managed path will add it to the hosts file [20932]

When specifying a host named site collection to be created which are located under a managed path, AutoSPInstaller will add the complete URL to the hosts file. I.e. when I use a HNSC scenario so I have to use HNSC to create site collections which reside under an URL which is not a physical web application and my host webapplication is hosted under https://sharepoint.zomers.eu and I want to create a site collection under https://www.zomers.eu/sites/something, I need to have it created as a HNSC. This works fine, however AutoSPInstaller will also add www.zomers.eu/sites/something to the hosts file of Windows while this has no function. It should only add the HNSC to the hosts file if it is not under a managed path, so i.e. www.zomers.eu is fine.
Comments: Resolved with changeset 108460: Changes in this release:

- Fixes for AddToHOSTS function to skip adding local computer name to HOSTS file (issue 19998) and to avoid including path info in the HOSTS file entry in cases where host-named site collections are used (issue 20932)
- Check for and if necessary remove trailing slash from the data directory (issue 20884)
- Updated ConfigureFarmAdmin function to add Farm Account to local admins (temporarily) if either explicitly requested, or if either user profile service app or distributed cache is being provisioned on local server (per @harbars)
- Updated CreateOrJoinFarm function to leverage -SkipRegisterAsDistributedCacheHost switch when joining/creating farm and be more verbose
- Updated AutoSPInstallerInput.xml to use "CONTOSO" for the domain of sample accounts, and proper FQDNs for URLs - makes search & replace easier and discourages using http:// (i.e. localhost) for URLs