RFC: Custom Global Domain Name Patterns

### Describe the feature

It'd be great to have a way to set a domain name pattern at the app or stack level that can be defaulted to in constructs.

### Use Case

I find that many times there's copy and pasted logic not only in repos, but spread across repos to handle structuring domains names for endpoints. It seems like teams usually follow common patterns such as `..`, etc.

Some of the copy and pasted code includes:

- Constants file for hosted zones
- Logic for building a domain (see example above), even within one CDK app, such as for CloudFront + API Gateway
- Different teams might also have different domain patterns depending on their architecture. So it makes it challenging to embed opinionated logic about the domain structure in an internal CDK library.

### Proposed Solution

It seems like this could be solved a number of ways including:

- A `domainNamePattern` context key or SSM parameter
- A tag on a hosted zone that marks it as default for the account
- Property injection or aspects that override the domain name for individual resources

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### AWS CDK Library version (aws-cdk-lib)

2.222.1

### AWS CDK CLI version

2.1031.1

### Environment details (OS name and version, etc.)

Mac OS

No files, tests, or entry points are named. Start by examining how AWS CDK app and stack context reaches constructs, then compare the proposed context, SSM, hosted-zone tag, and aspect approaches; done requires an agreed design for domain-pattern defaults and its implementation scope.

Written by the indexing model from the issue text.