feat(route53): adding access logging possibility to the resulting Cloudfront distribution created by the redirect construct

[roland-gharfine]

Issue # (if applicable)

N/A

Reason for this change

For compliance and security reasons, an organisation might want to enable access logging on all Cloudfront distributions. This PR allows to maintain governance and adherence to security configuration standards without manual intervention.

Description of changes

• Allowing the callers of the patterns.HttpsRedirect() construct to pass an optional parameter of type LoggingConfig (existing interface)
• Creating an object of type
• Setting the loggingConfig property of this object if it's passed to the construct
• Calling the CloudFrontWebDistribution() construct with the CloudFrontWebDistributionProps object rather than setting the properties inline

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 3207769
• Result: FAILED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[aws-cdk-automation]

This PR has been in the CHANGES REQUESTED state for 3 weeks, and looks abandoned. To keep this PR from being closed, please continue work on it. If not, it will automatically be closed in a week.

[aws-cdk-automation]

This PR has been deemed to be abandoned, and will be automatically closed. Please create a new PR for these changes if you think this decision has been made in error.

[aws-cdk-automation]

The pull request linter fails with the following errors:

❌ Features must contain a change to a test file.
❌ Features must contain a change to an integration test file and the resulting snapshot.

PRs must pass status checks before we can provide a meaningful review.

If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing Exemption Request and/or Clarification Request.