fix(aws-cloudfront-s3): do not create s3 access log bucket for cf log bucket when an existing bucket is provided

[biffgaut]

Description of changes:
In this situation:

  const cfS3AccessLogBucket = new s3.Bucket(stack, 'cf-s3-access-logs');
  new CloudFrontToS3(stack, 'test-cloudfront-s3', {
    cloudFrontLoggingBucketProps: {
      serverAccessLogsBucket: cfS3AccessLogBucket
    }
  });

The construct will still create an S3 Access Log bucket for the CF log bucket. The provided bucket is ignored. What should happen is that the provided bucket is configured to accept the logs and no additional bucket is created.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[aws-solutions-constructs-team]

AWS CodeBuild CI Report

• CodeBuild project: githubautobuild-for-cdk-v2
• Commit ID: 7eebd22
• Result: SUCCEEDED
• Build Logs (available for 30 days)

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

[georgebearden]

looks good to me