Merge pull request newrelic#16972 from newrelic/OTEL-info-rearchitecture

chore(OTEL): reorganize OTEL docs, remove legacy exporters doc

src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction.mdx

@@ -181,7 +181,7 @@ New Relic supports the native OpenTelemetry Protocol (OTLP) for exporting teleme
 The tables in the sections below show the supported features for each telemetry signal. If you have any questions about details in the sections below or unsupported use cases, please contact us in our [CNCF Slack channel](https://cloud-native.slack.com/archives/C024DRQ63UP), and watch this page for future updates. If you prefer to get the big picture of an implementation with New Relic, see our [reference architecture](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-ref-architecture).
 
 <Callout variant="important">
-  [New Relic's exporters](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-legacy-new-relic-exporters) for OpenTelemetry are now deprecated in favor of exporting data to New Relic using OTLP.
+  New Relic's exporters for OpenTelemetry are now deprecated in favor of exporting data to New Relic using OTLP.
 </Callout>
 
 ### Traces [#trace-ingest]

src/i18n/content/es/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction.mdx

@@ -163,7 +163,7 @@ New Relic admite el protocolo nativo OpenTelemetry (OTLP) para exportar telemetr
 Las tablas de las secciones siguientes muestran las características admitidas para cada señal de telemetría. Si tiene alguna pregunta sobre los detalles de las secciones siguientes o casos de uso no compatibles, contáctenos en nuestro [canal CNCF Slack](https://cloud-native.slack.com/archives/C024DRQ63UP) y mire esta página para futuras actualizaciones. Si prefiere obtener una visión general de una implementación con New Relic, consulte nuestra [arquitectura de referencia](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-ref-architecture).
 
 <Callout variant="important">
-  [Los exportadores de New Relic](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-legacy-new-relic-exporters) para OpenTelemetry ahora están en desuso a favor de exportar datos a New Relic usando OTLP.
+  Los exportadores de New Relic para OpenTelemetry ahora están en desuso a favor de exportar datos a New Relic usando OTLP.
 </Callout>
 
 ### Traza [#trace-ingest]

src/i18n/content/jp/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction.mdx

@@ -153,7 +153,7 @@ OpenTelemetryはまだ始まったばかりの規格なので、利用可能な
 [以下のセクションの表は、各テレメトリー信号でサポートされている機能を示しています。以下のセクションの詳細やサポートされていないユースケースについて質問がある場合は、 ](https://github.com/open-telemetry/opentelemetry-specification/blob/master/spec-compliance-matrix.md)[CNCF Slackチャンネル](https://cloud-native.slack.com/archives/C024DRQ63UP) までご連絡ください。また、このページで今後の更新をご確認ください。New Relic を使った実装の全体像を把握したい場合は、 [リファレンスアーキテクチャ](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-ref-architecture) をご覧ください。
 
 <Callout variant="important">
-  [New Relic の exporters](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-legacy-new-relic-exporters) for OpenTelemetry は現在非推奨となっており、OTLP を使用して New Relic にデータをエクスポートすることが推奨されています。
+  New Relic の exporters for OpenTelemetry は現在非推奨となっており、OTLP を使用して New Relic にデータをエクスポートすることが推奨されています。
 </Callout>
 
 ### トレース [#trace-ingest]

src/i18n/content/kr/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction.mdx

@@ -161,7 +161,7 @@ New Relic의 APM 에이전트는 개별 서비스에 대한 자세한 트랜잭
 아래 섹션의 표는 각 원격 측정 신호에 대해 지원되는 기능을 보여줍니다. 아래 섹션의 세부 정보나 지원되지 않는 사용 사례에 대해 질문이 있는 경우 [CNCF Slack 채널](https://cloud-native.slack.com/archives/C024DRQ63UP) 에서 문의하고 이 페이지에서 향후 업데이트를 확인하세요. New Relic으로 구현에 대한 큰 그림을 보고 싶다면 [참조 아키텍처](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-ref-architecture) 를 참조하십시오.
 
 <Callout variant="important">
-  [New Relic's 수출기업](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-legacy-new-relic-exporters) for Open텔레메트리는 이제 OTLP를 사용하여 데이터를 New Relic (Relic to New Relic) 로 내보내는 데 더 이상 사용되지 않습니다.
+  New Relic's 수출기업 for Open텔레메트리는 이제 OTLP를 사용하여 데이터를 New Relic (Relic to New Relic) 로 내보내는 데 더 이상 사용되지 않습니다.
 </Callout>
 
 ### 트레이스 [#trace-ingest]

src/i18n/content/pt/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-introduction.mdx

@@ -163,7 +163,7 @@ A New Relic oferece suporte ao OpenTelemetry Protocol (OTLP) nativo para exporta
 As tabelas nas seções abaixo mostram os recursos suportados para cada sinal de telemetria. Se você tiver alguma dúvida sobre os detalhes nas seções abaixo ou casos de uso não suportados, entre em contato conosco em nosso [canal CNCF Slack](https://cloud-native.slack.com/archives/C024DRQ63UP) e observe esta página para atualizações futuras. Se você preferir ter uma visão geral de uma implementação com New Relic, consulte nossa [arquitetura de referência](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-ref-architecture).
 
 <Callout variant="important">
-  [Os exportadores da New Relic](/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-legacy-new-relic-exporters) para OpenTelemetry agora estão obsoletos em favor da exportação de dados para a New Relic usando OTLP.
+  Os exportadores da New Relic para OpenTelemetry agora estão obsoletos em favor da exportação de dados para a New Relic usando OTLP.
 </Callout>
 
 ### Traces [#trace-ingest]