Missing customHttpsParameters property in Azure CDN REST API

CustomDomains response definition does not include `customHttpsParameters` in latest api version. When you run the REST API, the following is actually included.

```
# Status: 200

# content-encoding: gzip
# content-type: application/json; charset=utf-8
# date: Tue, 09 Feb 2021 16:13:30 GMT
# expires: -1
# instance-name: explorer-hk1
# request-context: appId=cid-v1:a7a0aa45-52ad-43f4-a8c4-8896f1392829
# strict-transport-security: max-age=31536000; includeSubDomains
# transfer-encoding: chunked
# vary: Accept-Encoding
# x-content-type-options: nosniff
# x-ms-client-request-id: 34fc7cdd-f6c1-4540-9a11-d5680985c3bf
# x-ms-correlation-request-id: 994de376-60a2-400d-b824-3bbc430c5964
# x-ms-ellapsed: 1599ms
# x-ms-ratelimit-remaining-subscription-reads: 11999
# x-ms-request-id: 1ffe6285-5920-4aaf-995e-09badcc10be4
# x-ms-routing-request-id: EASTASIA:20210209T161330Z:994de376-60a2-400d-b824-3bbc430c5964
{
"value": [
{
"id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourcegroups/**/providers/Microsoft.Cdn/profiles/**/endpoints/**/customdomains/daruyanagi-com",
"type": "Microsoft.Cdn/profiles/endpoints/customdomains",
"name": "daruyanagi-com",
"properties": {
"hostName": "daruyanagi.com",
"validationData": null,
"resourceState": "Active",
"customHttpsProvisioningState": "Enabled",
"customHttpsProvisioningSubstate": "CertificateDeployed",
"customHttpsParameters": {
"certificateSource": "AzureKeyVault",
"certificateSourceParameters": {
"subscriptionId": "00000000-0000-0000-0000-000000000000",
"resourceGroupName": "**",
"vaultName": "**",
"secretName": "daruyanagi-com",
"secretVersion": "5c769c2c98054127bf4400f67a2e8751",
"updateRule": "NoAction",
"deleteRule": "NoAction",
"@odata.type": "#Microsoft.Azure.Cdn.Models.KeyVaultCertificateSourceParameters"
},
"protocolType": "ServerNameIndication",
"minimumTlsVersion": "TLS12"
},
"provisioningState": "Succeeded"
}
}
]
}
```

Start by locating the latest Azure CDN CustomDomains response definition in the REST API specifications and compare it with the response shown in the issue. Add the missing customHttpsParameters representation, then run the repository's relevant specification validation. Done means the property is included for the affected API version without breaking validation.

Written by the indexing model from the issue text.