v1.0.0

feat: Backport cloudposse/cloudfront-cdn/aws improvements Jakub Wądołowski (@jwadolowski) (#340)

## what

Backport of the following cloudposse/terraform-aws-cloudfront-cdn improvements:

• cloudposse/terraform-aws-cloudfront-cdn#140
• cloudposse/terraform-aws-cloudfront-cdn#142
• cloudposse/terraform-aws-cloudfront-cdn#147
• cloudposse/terraform-aws-cloudfront-cdn#149

Detailed breakdown:

• aws_s3_bucket_cors_configuration is deployed only when at least one CORS origin is defined (examples/complete/minimal.tf fails if this isn't handled)
• don't use lookup() (or any other default variable value fallback method) - all defaults should be defined in the variables.tf file
• wrap optional variables with optional() and provide sane defaults (in most cases that'd be empty string/list/null or predefined AWS default when applicable, e.g. timeout values)
• default origin
  • add origin_keepalive_timeout and origin_read_timeout
• custom origin improvements
  • enable shield configuration
• custom s3 origins
  • allow for shield configuration
  • fix origin_access_control_id assignment (origin.value.s3_origin_config.origin_access_control_id doesn't exist, but origin.value.origin_access_control_id does)
• ordered cache improvements
  • gRPC support
• cookie block should set whitelisted_names param only when forward=whitelist (in all other cases, all and none, the whitelisted_names is automatically set to null)

why

Both CloudPosse CDN modules should stay in sync (feature-wise) and leverage the same set of improvements.

references

• includes #347 to re-generate docs after changes. #347 should get merged first