Fix addon instantiation ordering and clean deletion

[ytsarev]

Description of your changes

• Import eks security group for full control over it
• Enable vpc-cni addon for explicit configuration with preserve: false
• Create addons after nodegroup creation. Before this change, the csi addon stuck in the degraded state for more than 20 minutes
• Now, with a proper ordering, the addons are ready almost immediately after instantiation

NAME                                                   READY   SYNCED   EXTERNAL-NAME                                    AGE
addon.eks.aws.upbound.io/configuration-aws-eks-dkwcw   True    True     configuration-aws-eks-4n8fl:aws-ebs-csi-driver   112s
addon.eks.aws.upbound.io/configuration-aws-eks-sq5z6   True    True     configuration-aws-eks-4n8fl:vpc-cni              112s

context on leaked ENIs deletion

terraform-aws-modules/terraform-aws-eks#2743 (comment)
aws/amazon-vpc-cni-k8s#1223 (comment)
aws/amazon-vpc-cni-k8s#69
aws/amazon-vpc-cni-k8s#2360

I have:

• Read and followed Upbound's contribution process.
• Run make reviewable to ensure this PR is ready for review.
• Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested

=== CONT  kuttl
    harness.go:402: run tests finished
    harness.go:511: cleaning up
    harness.go:553: skipping cluster tear down
    harness.go:554: to connect to the cluster, run: export KUBECONFIG="/Users/xnull/upbound/configuration-aws-eks/kubeconfig"
--- PASS: kuttl (2066.23s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/case (2065.73s)
PASS
12:00:06 [ OK ] running automated tests

[ytsarev]

/test-examples