[Content Refresh] Update EKS Observability workshop — EKS version, OTEL guidance, screenshots

### What would you like to be added?

The EKS Observability workshop has several outdated elements that need updating:

1. **Outdated screenshots and names** — several console screenshots no longer match current UI.

- No longer "Log Insights" -> it is "Log Analytics"
- "Verify the logs in cloudwatch" at Pod Logging is outdated - you have to search with the name of the Log group created by FLuentbit, which can be checked using the configmap
- At Kubecost lab, screenshots are outdated

2. **OTEL add-on and Open Source Observability** — We should shift our focus to AWS CloudWatch Agent which uses FluentBit and OTEL in the background. I would apply this change specifically at Open Source Observability Lab:

- **Telemetry → CloudWatch/Xray/Prometheus**: Use the **CloudWatch Agent add-on** (now supports OpenTelemetry + PromQL)
- **Telemetry → external backends**: Use upstream OpenTelemetry Collectors
- **Extra**: also on OSS Observability Lab I would suggest documenting why AMG is preferrable in AWS to self-managed Grafana, documenting the partnership AWS has with Grafana and perks from it - without requiring Grafana enterprise license

3. **Container Insights activation** — Should follow the current recommended quickstart method via EKS add-on: [https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/container-insights-eks-otel-quickstart.html](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/container-insights-eks-otel-quickstart.html)

### Why is this needed?

This workshop is actively used for customer enablement sessions. Outdated cluster versions, deprecated OTEL patterns, and stale screenshots erode credibility and can lead customers to implement approaches that are no longer recommended — creating technical debt from day one.

Locate the EKS Observability workshop sections for Pod Logging, the Kubecost lab, Open Source Observability, and Container Insights. Compare their current guidance and screenshots with the linked AWS Container Insights quickstart and verify the terminology and recommended telemetry paths. Done means the workshop reflects current EKS and observability guidance, including refreshed screenshots and the requested AMG context.

Written by the indexing model from the issue text.