active-directory-new-domain-ha-2-dc template does not work with Windows Server 2016

active-directory-new-domain-ha-2-dc

### Issue Details
The DSC script fails when deploying to Windows Server 2016:
{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 'CreateADForest'. Error message: \"DSC Configuration 'CreateADPDC' completed with error(s). Following are the first few: Verification of prerequisites for Domain Controller promotion failed. The specified argument 'DataBasePath' was not recognized.\r\n The PowerShell DSC resource '[xADDomain]FirstDS' with SourceInfo 'C:\\Packages\\Plugins\\Microsoft.Powershell.DSC\\2.23.0.0\\DSCWork\\CreateADPDC.ps1.0\\CreateADPDC.ps1::81::9::xADDomain' threw one or more non-terminating errors while running the Set-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details. The SendConfigurationApply function did not succeed.\"."
}
]
}
}

### Repro steps (*if necessary, delete otherwise*)
1. From the repo or quickstarts web, click the deploy to Azure button
2. Fill in required fields
3. Change the Image Sku parameter from 2012-R2-Datacenter to 2016-Datacenter
4. Deploy
5.

Locate the active-directory-new-domain-ha-2-dc template and its CreateADPDC DSC configuration, then review the xADDomain FirstDS resource and the Windows Server image SKU parameter. Reproduce the deployment using 2016-Datacenter and inspect the DSC/ETW failure. Done means the template deploys successfully on Windows Server 2016 without the DataBasePath argument error.

Written by the indexing model from the issue text.