Polish "Remove HierarchicalNameMapper as a configured @bean"

Closes gh-12683

Author: snicoll

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/metrics/export/ganglia/GangliaMetricsExportAutoConfiguration.java

@@ -62,4 +62,5 @@ public GangliaMeterRegistry gangliaMeterRegistry(GangliaConfig gangliaConfig,
 			Clock clock) {
 		return new GangliaMeterRegistry(gangliaConfig, clock);
 	}
+
 }

spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/metrics/export/jmx/JmxMetricsExportAutoConfiguration.java

@@ -61,4 +61,5 @@ public JmxConfig jmxConfig(JmxProperties jmxProperties) {
 	public JmxMeterRegistry jmxMeterRegistry(JmxConfig config, Clock clock) {
 		return new JmxMeterRegistry(config, clock);
 	}
+
 }

spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc

@@ -1435,11 +1435,12 @@ to use can be provided using:
 	management.metrics.export.graphite.port=9004
 ----
 
-Micrometer provides a default `HierarchicalNameMapper` that governs
-how a dimensional meter id is mapped to flat hierarchical names.
+Micrometer provides a default `HierarchicalNameMapper` that governs how a dimensional
+meter id is mapped to flat hierarchical names.
 
-TIP: To take control over this behaviour, define your `GraphiteMeterRegistry` and supply your
-own `HierarchicalNameMapper`.
+TIP: To take control over this behaviour, define your `GraphiteMeterRegistry` and supply
+your own `HierarchicalNameMapper`. An auto-configured `GraphiteConfig` and `Clock` beans
+are provided unless you define your own:
 
 [source,java]
 ----
@@ -1449,6 +1450,8 @@ public GraphiteMeterRegistry graphiteMeterRegistry(GraphiteConfig config, Clock
 }
 ----
 
+
+
 [[production-ready-metrics-export-influx]]
 ==== Influx
 By default, metrics are exported to {micrometer-registry-documentation}/influx[Influx]
@@ -1470,7 +1473,8 @@ view metrics locally. Micrometer provides a default `HierarchicalNameMapper` tha
 how a dimensional meter id is mapped to flat hierarchical names.
 
 TIP: To take control over this behaviour, define your `JmxMeterRegistry` and supply your
-own `HierarchicalNameMapper`.
+own `HierarchicalNameMapper`. An auto-configured `JmxConfig` and `Clock` beans are
+provided unless you define your own:
 
 [source,java]
 ----
@@ -1480,6 +1484,8 @@ public JmxMeterRegistry jmxMeterRegistry(JmxConfig config, Clock clock) {
 }
 ----
 
+
+
 [[production-ready-metrics-export-newrelic]]
 ==== New Relic
 New Relic registry pushes metrics to {micrometer-registry-documentation}/new-relic[New