agent-platform release v4.80.0

The kagent line at 1.2.0, and kagent.otel in the chart’s SDK-spec shape (giantswarm/giantswarm#37742). components.kagent.versionRange and components.kagent-crds.versionRange are >=1.2.0 <1.3.0 (upstream kagent main@dd3b2405, Substrate 1.1.0 unchanged). kagent.otel is exporter.otlp.{endpoint,protocol,timeout} (auto, auto, "500": endpoint and protocol follow global.observability.traces.otlp), traces.enabled and logs.enabled (auto, off while the signal has no endpoint); kagent.otel.tracing and kagent.otel.logging are gone, and so is their insecure (the endpoint’s scheme decides), and so are OTEL_LOGGING_ENABLED and KAGENT_TRACE_FLUSH_TIMEOUT_MS in kagent.harness.env. The connectivity chart reads the same shape for the OTLP egress rules of the kagent controller and the Substrate egress gateway: a signal’s own endpoint and protocol, else exporter.otlp’s. UPGRADE.md. The kagent log exporter honors the protocol on this line, so global.observability.traces.otlp.protocol: http/protobuf no longer fails the render over it.