New Pattern: aws-route53-acm-cloudfront

It is often necessary to use a custom domain with SSL certificate on a CloudFront distribution. While existing patterns like aws-s3-cloudfront can serve files, setting up custom domain for the CloudFront and attaching SSL certificates needs additional work. This is particularly hard for someone who is not familiar setting up certificates and DNS records. The proposed construct will make it easy to create CloudFront distributions that is ready for production with custom domain and SSL certificate.

### Use Case
- The proposed construct can be used along with aws-s3-cloudfront construct to deploy static websites with custom domain and SSL certificate.
- The proposed construct can be used along with aws-cloudfront-apigateway to create custom, secure endpoints for user facing APIs.

### Proposed Solution
The proposed construct has the following features:
- Automatically verify domain ownership and provision SSL certificate using ACM. (Fully automatic if Route53 is used as the DNS service.)
- Import an existing SSL certificate using its ARN.
- Configure cloudFront to use custom domain by adding alias configuration.
- Use incoming hosted zone or create one and then link it to CloudFront using Alias record.

### Other
I have used this pattern in multiple prototypes and a solution construct of this pattern can made the CDK script shorter and elegant.

* [x] :wave: I may be able to implement this feature request
* [ ] :warning: This feature might incur a breaking change

---

This is a :rocket: Feature Request

Start by reviewing the existing aws-s3-cloudfront and aws-cloudfront-apigateway constructs mentioned in the issue, then examine how the repository structures similar patterns. Done should cover ACM certificate provisioning or import, custom-domain aliases, hosted-zone handling, and Route53 integration for CloudFront.

Written by the indexing model from the issue text.