Install cluster-wide kube-prometheus-stack through wallet-eks-env Terraform

### Decision
Reuse adorsys/wallet-eks-env. Do not create adorsys/cluster-monitoring, an umbrella Helm chart, or a second Argo CD owner for the monitoring stack.

### Scope

Extend the existing local EKS Blueprints Addons wrapper to expose enable_kube_prometheus_stack and its configuration.
Deploy chart 88.6.2 into namespace monitoring, explicitly pinned.
Configure cross-namespace, label-opt-in discovery for ServiceMonitors, PodMonitors, PrometheusRules, Probes/ScrapeConfigs, and AlertmanagerConfigs.
Keep Alertmanager's OnNamespace matcher strategy.
Configure encrypted EBS persistence, bounded retention, resource requests/limits, and internal-only services.
Reuse the existing ESO installation and IRSA; add only exact monitoring secret permissions.
Provision Grafana admin credentials from AWS Secrets Manager.
Handle EKS managed control-plane targets to avoid false alerts.
Verify the Status List /metrics and ServiceMonitor path end to end.
Track the Status List AlertmanagerConfig API correction, namespace-scoped PromQL, dashboard ConfigMap, and 30-day retention dependency as linked application work.
Document application onboarding and operational verification.

EST: 3 days