Address review comments for OpenTelemetry API support page

Addresses feedback from @hannahramadan, @tippmar-nr, and @jasonjkeller:

- Simplify 'Not supported' statements by removing redundant 'is not currently available' text
- Clarify Java bytecode auto-instrumentation wording: it's not detected, not that it conflicts
- Update limitations table to reflect 'not detected' instead of 'conflicts'

Changes made:
- Metrics/Logs/Span Links/Events: Simplified to '❌ Not supported: [Feature]'
- Java bytecode: Changed from 'not compatible...conflicts' to 'will not be detected'
- Consistent messaging across documentation and limitations sections

Author: cbehera-newrelic

src/content/docs/apm/agents/manage-apm-agents/opentelemetry-api-support.mdx

@@ -200,7 +200,7 @@ OpenTelemetry API support is disabled by default. Enable it through your agent's
     Custom instrumentation using the OpenTelemetry trace, metrics, or logs APIs will be automatically captured by the agent.
 
     #### Library and native instrumentation
-    OpenTelemetry standalone library instrumentations and native instrumentation built directly into libraries will work with the New Relic agent. However, OpenTelemetry bytecode-based auto-instrumentation is not compatible with the New Relic agent and will not be detected.
+    OpenTelemetry standalone library instrumentations and native instrumentation built directly into libraries will work with the New Relic agent. However, OpenTelemetry bytecode-based auto-instrumentation will not be detected by the New Relic agent.
   </Collapser>
 
   <Collapser
@@ -415,16 +415,16 @@ OpenTelemetry API support is disabled by default. Enable it through your agent's
     ✅ **Supported**: Create custom spans and add attributes using the OpenTelemetry Tracing API
 
     #### Metrics API
-    ❌ **Not supported**: OpenTelemetry Metrics API is not currently available
+    ❌ **Not supported**: OpenTelemetry Metrics API
 
     #### Logs API
-    ❌ **Not supported**: OpenTelemetry Logs API is not currently available
+    ❌ **Not supported**: OpenTelemetry Logs API
 
     #### Span Links
-    ❌ **Not supported**: Span Links are not currently available
+    ❌ **Not supported**: Span Links
 
     #### Events on Spans
-    ❌ **Not supported**: Events on Spans are not currently available
+    ❌ **Not supported**: Events on Spans
 
     ### How it works
 
@@ -488,9 +488,9 @@ After enabling OpenTelemetry API support, verify that it's working:
       </td>
     </tr>
     <tr>
-      <td>Java bytecode instrumentation conflicts</td>
+      <td>Java bytecode instrumentation not detected</td>
       <td>
-        Java OpenTelemetry auto-instrumentation that uses bytecode manipulation is not supported due to technical conflicts with the New Relic agent's bytecode instrumentation.
+        Java OpenTelemetry auto-instrumentation that uses bytecode manipulation will not be detected by the New Relic Java agent.
       </td>
     </tr>
   </tbody>