Add auto-configuration for OtlpMeterRegistry

See gh-30825

spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/metrics.adoc

@@ -14,6 +14,7 @@ Spring Boot Actuator provides dependency management and auto-configuration for h
 - <<actuator#actuator.metrics.export.jmx,JMX>>
 - <<actuator#actuator.metrics.export.kairos,KairosDB>>
 - <<actuator#actuator.metrics.export.newrelic,New Relic>>
+- <<actuator#actuator.metrics.export.otlp,OpenTelemetry>>
 - <<actuator#actuator.metrics.export.prometheus,Prometheus>>
 - <<actuator#actuator.metrics.export.signalfx,SignalFx>>
 - <<actuator#actuator.metrics.export.simple,Simple (in-memory)>>
@@ -437,6 +438,22 @@ Finally, you can take full control by defining your own `NewRelicClientProvider`
 
 
 
+[[actuator.metrics.export.otlp]]
+==== OpenTelemetry
+By default, metrics are exported to {micrometer-registry-docs}/otlp[OpenTelemetry] running on your local machine.
+You can provide the location of the https://opentelemetry.io/[OpenTelemtry metric endpoint] to use by using:
+
+[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
+----
+	management:
+	  otlp:
+	    metrics:
+	      export:
+	        url: "https://otlp.example.com:4318/v1/metrics"
+----
+
+
+
 [[actuator.metrics.export.prometheus]]
 ==== Prometheus
 {micrometer-registry-docs}/prometheus[Prometheus] expects to scrape or poll individual application instances for metrics.