Support wildcard DV certificates and subdomains

[#1]

Request for Feature Enhancement (RFE) Summary:	Wildcard DV certificates and wildcard subdomains
Use-case:	For DEV and STAGE environments often a common publish domain is being used. As the default Adobe one (https://publish-pxxx-eyyy.adobeaemcloud.com/) does not allow subdomains the individual sites are addressed via subdomains of that common domain to have a similar setup as PROD (1 domain = 1 website). That allows even automatic mapping of content paths to sites without needing setup costs for additional sites.
Current/Experienced Behavior:	Cloud Manager does neither support wildcard domains in the domain settings (https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/usi...) nor does it allow wildcard DV Adobe-managed certificates. Therefore each subdomain requires - Configuration via the Domain - Domain verification via additional TXT record - Set up a dedicated DV manager certificate Although one could use a custom wildcard certificate right now, that needs to be OV/EV (too expensive for DEV/STAGE purposes) and also the management per subdomain still needs to be done manually.
Improved/Expected Behavior:	Allow wildcard domains so that the setup is only necessary once, instead of per sub domain. This requires: - Allow configuration of wildcard domains in Domain management - Allow Adobe managed DV certificates for wildcards (supported by Let's Encrypt with every ACMEv2 compatible client) - Adjust UI to allow mapping the wildcard certificates to the wildcard domain
Environment Details (AEM version/service pack, any other specifics if applicable):	n/a
Customer-name/Organization name:
Screenshot (if applicable):
Code package (if applicable):