Upgrade cloudposse/s3-log-storage/aws to 1.0.0

[paulvandenburg]

This PR contains the following updates:

cloudposse/s3-log-storage/aws (source) module major 0.26.0 -> 1.0.0

Supersedes #250

Should fix failing CI.

[paulvandenburg]

After testing I think this is complete.

For the release notes perhaps recommend the various imports you might want to do so it won't try to create the likely already existing config. Since the split out s3 resources causes this.

Importing is as simple as mentioning the various new s3 resources with the related bucket name:

• aws_s3_bucket_acl
• aws_s3_bucket_server_side_encryption_configuration
• aws_s3_bucket_versioning
• aws_s3_bucket_logging
• aws_s3_bucket_website_configuration
• aws_s3_bucket_cors_configuration
• aws_s3_bucket_lifecycle_configuration

Trial and error might be easiest here since various setups trigger various sets of those appearing in your terraform plan.
As it could come from all of this modules main.tf, the nested logs module or the logs module's nested s3-bucket module.