Please describe the feature request.
ExponentialHistogram was proposed in this OTEP (OpenTelemetry Enhancement Proposal) and was made stable by open-telemetry/opentelemetry-specification#3041. Exponential Histograms advantages are documented in the OpenTelemetry documents to list a few - configuration free, can record highly dynamic values, fully mergeable (the merging is lossy but errorless).
Micrometer should support exporting ExponentialHistogram when the export happens through OTLPMeterRegistry. The expectation is that for the use-case where service level objectives are defined, we will continue to use ExplicitBucketHistograms (It completely makes sense for a use-case where the objective is to track/observe the signals based on a set of pre-defined SLAs rather than the auto-generated one and also very cheaper when there are less SLO's involved), but when percentilesHistogram() is enabled the flavor of the histogram can either be ExplicitBucketHistogram or ExponentialHistogram based on the config supplied during Registry creation time (there is also an environmental variable available for this).

Rationale
This allows the export of ExponentialHistogram for which some of the benefits are mentioned above.

References:

• Mark base-2 exponential histogram as stable open-telemetry/opentelemetry-specification#3041
• Stabilize exponential histograms open-telemetry/opentelemetry-specification#2832
• Define configurable max scale for exponential histogram aggregation open-telemetry/opentelemetry-specification#2987