Add configuration options for AWS S3 server access logging

[findmyname666]

Description

Fixes #3003.

In our environment the S3 bucket where should be stored S3 access logs is pre-created by "central" team and we don't have permissions to do any changes. In such case we don't have to:

• Create it - the current code creates the logging bucket only if it doesn't exist. No change is needed.
• Configure logging bucket e.g. ACL, public access, encryption, tls enforcement - adding option to skip the configuration for access log bucket.
• PartitionDateSource - Adding one more option to allow users to configure PartitionDateSource.

Additionally 1) adding error logging into the function configureAccessLogBucket. Without it I wasn't able to detect why the policy isn't configured. The error is returned but ignored. 2) Adding code to detect if the logging policy / configuration was change. The previous code just check if some policy is enabled.

TODOs

Read the Gruntwork contribution guidelines.

• Update the docs.
• Run the relevant tests successfully, including pre-commit checks.
• Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
• Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].

Migration Guide

N/A.

[findmyname666]

I did typo in a branch name so I created a new PR #3006.