Support adding custom domains to Aspire apps deployed via ACA

[mitchdenny]

Over in the Aspire repo we got this feature request:

dotnet/aspire#1322

This is more of a deployment time concern as the domain you want to apply would be different for each environment that you are deploying into. Custom domain support for publicly exposed endpoints pulls in a few considerations such as support for certificates. I know when I've automated this in the past with Bicep you end up needing to have an Azure DNS domain which you can create your sub domain off so that you can use Bicep to inject the necessary TXT records at deployment to allow auto certificate generation.

[KSemenenko]

As I know there are two ways to make this.Depends on DNS.

In one case in our DNS we have to add IP address for our service, and probably some other records. So this is more complicated.

And second when we can use Azure DNS.

I prefer Azure DNS

[rajeshkamal5050]

Duplicate of #1765