feat: use security-group module instead of resource

[SweetOps]

what

• use security-group module instead of resource
• update tests

why

• more flexible than current implementation
• bring configuration of security group/rules to one standard

references

• CPCO-409

[SweetOps]

/test all

[SweetOps]

/test all

[nitrocode]

/test all

[z0rc]

When upgrading module for existing cluster to this version, the change triggers security group recreation, which triggers EKS cluster recreation. Which is really not an expected thing to happen on minor version bump. I had to do manual

terraform state mv 'module.eks.aws_security_group.default[0]' 'module.eks.module.security_group.aws_security_group.default[0]'

to keep terraform from recreating half of the stack.

Just a small request to maintainers be a bit more mindful about upgrade paths.