chore(eks-v2): update integ tests for eks-addon and eks-cluster-removal-policy

[aemada-aws]

Issue # (if applicable)

N/A

Reason for this change

Two aws-eks-v2 integration tests needed fixes to deploy successfully:

1. integ.eks-addon: Used coredns as the addon under test, which conflicts with the default EKS-managed coredns addon installed on every cluster. This caused deployment and teardown failures, requiring expectError: true on destroy as a workaround.
2. integ.eks-cluster-removal-policy: Used a hardcoded fake IAM ARN (arn:aws:iam::123456789012:user/test-user) for the AccessEntry principal, which fails deployment since the ARN doesn't exist. The HelmChart also lacked an explicit dependency on the ALB Controller, causing intermittent failures when the webhook wasn't ready.

Description of changes

integ.eks-addon:

• Replace coredns addon with snapshot-controller to avoid conflict with the default EKS addon
• Preserve preserveOnDelete: true and configurationValues (using logLevel: 3) to maintain test coverage of addon configuration
• Remove expectError: true on destroy since snapshot-controller tears down cleanly

integ.eks-cluster-removal-policy:

• Replace hardcoded fake IAM ARN with a real iam.Role resource for the AccessEntry principal so the stack actually deploys
• Add explicit dependency from HelmChart to ALB Controller (helmChart.node.addDependency(albController)) to ensure the webhook is ready before chart installation
• Clarify comments to distinguish Pod Identity vs IRSA service accounts and document the HelmChart dependency
• Update snapshots via integ-runner

Describe any new or updated permissions being added

N/A

Description of how you validated changes

Both tests deployed and destroyed successfully:

yarn integ \
  test/aws-eks-v2/test/integ.eks-addon.js \
  test/aws-eks-v2/test/integ.eks-cluster-removal-policy.js \
  --disable-update-workflow \
  --update-on-failed \
  --force \
  --parallel-regions us-east-1 \
  --parallel-regions us-west-2 \
  --parallel-regions eu-west-1 \
  --verbose

  SUCCESS    aws-eks-v2/test/integ.eks-addon-EksClusterwithAddon/DefaultTest 2614.378s
  SUCCESS    aws-eks-v2/test/integ.eks-cluster-removal-policy-eks-cluster-removal-policy-integ/DefaultTest 2638.313s

Tests:    2 passed, 2 total

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
Please try merge from main to avoid findings unrelated to the PR.

---

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results	48 ran	48 passed

Test	Result
No test annotations available

• View Security Guardian Results

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
Please try merge from main to avoid findings unrelated to the PR.

---

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results with resolved templates	48 ran	48 passed

Test	Result
No test annotations available

• View Security Guardian Results with resolved templates