feat: add OpenTelemetry v2 docs

docs/develop/go/best-practices/context-propagation.mdx

@@ -16,13 +16,15 @@ tags:
 description: How to propagate custom key-value data across Workflow, Activity, and Child Workflow boundaries using the Temporal Go SDK.
 ---
 
-Context propagation lets you pass custom key-value data from a Client to Workflows, and from Workflows to Activities and Child Workflows, without threading it through every function signature. Common use cases include propagating tracing IDs, tenant IDs, auth tokens, or other request-scoped metadata.
+Context propagation lets you pass custom key-value data from a Client to Workflows, and from Workflows to Activities and Child Workflows, without threading it through every function signature. Common use cases include propagating tenant identifiers, auth tokens, or other request-scoped metadata.
 
 {/* TODO: Link to /encyclopedia/context-propagation once that page lands */}
 
 :::tip
 
-If you want to propagate tracing context, check if there is a [built-in tracing interceptor](/develop/go/platform/observability#tracing) for your library before building a custom context propagator.
+For OpenTelemetry tracing, use the [OpenTelemetry v2 integration](/develop/go/integrations/opentelemetry-v2). The plugin
+handles OpenTelemetry trace-context propagation automatically, so you do not need a custom Temporal context propagator
+for trace identifiers.
 
 :::
 

docs/develop/go/index.mdx

@@ -96,6 +96,7 @@ From there, you can dive deeper into any of the Temporal primitives to start bui
 ## [Integrations](/develop/go/integrations)
 
 - [Google ADK integration](/develop/go/integrations/google-adk)
+- [OpenTelemetry v2 integration](/develop/go/integrations/opentelemetry-v2)
 
 ## Temporal Go technical resources