Provide static IP as part of the outputs for non-custom domain support when using private VNET

[daconstenla]

Describe your changes

When connecting the container apps environment to a private VNET and you're not using custom domains you should configure a private DNS pointing to the ip according to the docs (link), quote:

Non-custom domains: If you don't plan to use custom domains, create a private DNS zone that resolves the Container Apps environment's default domain to the static IP address of the Container Apps environment. You can use Azure Private DNS or your own DNS server. If you use Azure Private DNS, create a Private DNS Zone named as the Container App environment’s default domain (..azurecontainerapps.io), with an A record. The A record contains the name * and the static IP address of the Container Apps environment. so when using private vnet private DNS can be configured

Issue number

There is no issue number.

Checklist before requesting a review

• [x] The pr title can be used to describe what this pr did in CHANGELOG.md file
• [x] I have executed pre-commit on my machine
• [x] I have passed pr-check on my machine

Thanks for your cooperation!