upload new otel agent sdk image (#2777)

Co-authored-by: Phillip Carter <pcarter@fastmail.com>

content/en/docs/collector/deployment/agent.md

@@ -15,7 +15,7 @@ daemonset).
 Each client-side SDK or downstream collector is configured with a collector
 location:
 
-![Decentralized collector deployment concept](../../img/agent-sdk.svg)
+![Decentralized collector deployment concept](../../img/otel_agent_sdk_v2.svg)
 
 1. In the app, the SDK is configured to send OTLP data to a collector.
 1. The collector is configured to send telemetry data to one or more backends.

content/en/docs/collector/deployment/gateway.md

@@ -14,7 +14,7 @@ deployment in Kubernetes), typically per cluster, per data center or per region.
 In the general case you can use an out-of-the-box load balancer to distribute
 the load amongst the collectors:
 
-![Gateway deployment concept](../../img/gateway-sdk.svg)
+![Gateway deployment concept](../../img/otel_gateway_sdk.svg)
 
 For use cases where the processing of the telemetry data processing has to
 happen in a specific collector, you would use a two-tiered setup with a

content/en/docs/collector/deployment/no-collector.md

@@ -8,7 +8,7 @@ The simplest pattern is not to use a collector at all. This pattern consists of
 applications [instrumented][instrumentation] with an OpenTelemetry SDK that
 export telemetry signals (traces, metrics, logs) directly into a backend:
 
-![No collector deployment concept](../../img/otel_sdk.png)
+![No collector deployment concept](../../img/otel_sdk.svg)
 
 ## Example