Fix cluster security group tags after security_group update

[ohayak]

Description

Use local.cluster_security_group_id instead aws_eks_cluster.this[0].vpc_config[0].cluster_security_group_id to refer to the actual cluster security group used by the cluster

Motivation and Context

We had a cluster up an running and we decided to change the naming of the cluster security groups:
As a side effect aws_eks_cluster kept the old security group reference in aws_eks_cluster.this[0].vpc_config[0].cluster_security_group_id and added the new security group id to additional security groups:
vpc_config {
cluster_security_group_id = "sg-old"
endpoint_private_access = false
endpoint_public_access = true
public_access_cidrs = [
"0.0.0.0/0",
]
security_group_ids = [
"sg-new",
]

[bryantbiggs]

this is not valid

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.