Add EKS Addon and IPv6 to OTelCI test

[Paamicky]

Description of the issue

The OTel Container Insights EKS e2e test only ran the Helm installation path and only on IPv4. The EKS add-on install path (now released) and IPv6 were not covered, unlike the JMX e2e suite which runs both Helm and add-on on IPv4/IPv6.

Description of changes

• EKSE2EOTELContainerInsightsTestHelmIPv6 (HELM_CHART, IPv6)
• EKSE2EOTELContainerInsightsTestAddonIPv6 (EKS_ADDON, IPv6)

The add-on jobs point at resources/cwagent_configs_eks_addon/ci_node.json and set eks_installation_type: EKS_ADDON; IPv6 jobs set ip_family: ipv6 and the IPv6 test VPC. Terraform and the test harness already support both install types.

Integration Tests

OTELContainerInsights EKS Addon and IPv6 test passed:Addon path and IPv6

---

License

By submitting this pull request, I confirm that you can use, modify, copy, and
redistribute this contribution, under the terms of your choice.

Requirements

1. Run make fmt and make fmt-sh
2. Run make lint

[olowosulu]

Minor issues ↓

• No evidence the new jobs were exercised. e2e-test.yml never runs on pull requests. Can you link a successful workflow_dispatch run of the three new jobs before merge?
• job_id input is a no-op (eks-e2e-test.yml L15). Declared required but never referenced here...

[Paamicky]

Minor issues ↓

• No evidence the new jobs were exercised. e2e-test.yml never runs on pull requests. Can you link a successful workflow_dispatch run of the three new jobs before merge?
• job_id input is a no-op (eks-e2e-test.yml L15). Declared required but never referenced here...

1. New jobs passed: https://github.com/aws/amazon-cloudwatch-agent/actions/runs/33828184956
2. job_id has been a no-op here since before this PR, so leaving it out of scope. Can file a follow-up to remove it.