fix: Change EKS addons to use EKS Blueprint addons module

[tiagoReichert]

Changed addons to blueprint

Description

Changing the addons from EKS to EKS Blueprints Addons fixed error messagens on vpc-cni.

Motivation and Context

• Resolves #

How was this change tested?

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I have updated the docs for this feature
• Yes, I ran pre-commit run -a with this PR

Additional Notes

[bryantbiggs]

what is the motivation for this change?

[tiagoReichert]

To remove the following message:

│ Warning: Argument is deprecated
│
│   with module.eks.aws_eks_addon.this["coredns"],
│   on .terraform/modules/eks/main.tf line 392, in resource "aws_eks_addon" "this":
│  392:   resolve_conflicts        = try(each.value.resolve_conflicts, "OVERWRITE")
│
│ The "resolve_conflicts" attribute can't be set to "PRESERVE" on initial resource creation. Use "resolve_conflicts_on_create" and/or "resolve_conflicts_on_update" instead
│
│ (and 2 more similar warnings elsewhere)

[bryantbiggs]

Unfortunately this won't remove that message

[tiagoReichert]

It worked here, can you try to reproduce?

[bryantbiggs]

oh nice, it does bypass that warning even though the deprecated resource is still there (though, not used)

Thank you! (ignoring the github action cache hit error - will monitor on subsequent PRs)