feat(OpenTelemetry): Add intent to upgrade OTLP notice.

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

@@ -33,6 +33,11 @@ Here are some best practices based on how OpenTelemetry works with New Relic:
   For information about resolving specific issues, see our [troubleshooting guide](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-troubleshooting).
 </Callout>
 
+
+<Callout variant="important">
+  Now that OpenTelemetry Protocol for Metrics is stable we intend to move our support from v0.10 to v0.16. This necessitates ending support for removed fields and data types, including the `Int` data point types for Metrics, `LogRecord.Name` for Logs, and status code for Traces.
+  Other significant changes include the renaming of `InstrumentationLibrary` to `InstrumentationScope`. We recommend upgrading your collector or instrumentation if you depend on removed or deprecated features. We expect to make this change during or after the week of April 18, 2022.
+</Callout>
 ## Resources [#resources]
 
 A resource in OpenTelemetry represents information about an entity generating telemetry data. All telemetry data sent to New Relic is expected to be associated with a resource so that it can be linked with the appropriate entity in New Relic. The [OpenTelemetry Resource SDK specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md) defines the functionality implemented by all language SDKs for defining a resource.