Upgrade to new securty-group standards

[Nuru]

what

• Upgrade to new Cloud Posse security group standards
• Enable proper operation when DNS zone is created at the same time as the cluster
• Enable create_before_destroy on security groups by default
• Update AWS provider version constraint to properly require a version that has all the features the module uses
• Add additional outputs for the Redis Replication Group

why

• Further standardize all Cloud Posse modules
• Supply bug fixes and features requested via "issues".

references

• Closes Count depends on resource to be created when zone_id is used #82
• Closes Use name_prefix and create_before_destroy on security groups #86
• Closes How to activate Multi-AZ option. #104
• Closes Additional outputs for the Redis Replication Group #113
• Closes v0.40.0 requires two runs to create & apply security group #121
• Closes Issues getting started: Sub-dependencies call variable errors #127
• Supersedes and closes chore(deps): update terraform cloudposse/security-group/aws to v0.4.0 #130
• Supersedes and closes Chore: bumps security group module version to 0.4.1 #132

Works around Terraform bug with using coalesce() or compact() in resource inputs.

[Nuru]

/test all

[aknysh]

When necessary, it will replace that security group with a new one
Not clear which one is "that" and which one is new (b/c the previous sentence says "This module creates, by default, a new security group").
Can you elaborate on this sentence?

[aknysh]

Suggested change

	use_legacy_egress = var.egress_cidr_blocks != null && var.egress_cidr_blocks != ["0.0.0.0/0"] && var.allow_all_egress != true
	use_legacy_egress = var.egress_cidr_blocks != null && !(length(var.egress_cidr_blocks) == 1 && var.egress_cidr_blocks[0] == "0.0.0.0/0") && var.allow_all_egress == false

Terraform does not support comparing lists using == and != operators, and can appear to work but will produce unexpected results

[aknysh]

LGTM, a few comments

[Nuru]

/test all