Micrometer tests fail because of OTel collector boot errors

[fabiobrz]

Micrometer related tests started to fail recently.

The server is unable to connect to the OTel collector:

2024-10-28 16:28:15,881 WARNING [io.micrometer.registry.otlp.OtlpMeterRegistry] (otlp-metrics-publisher) Failed to publish metrics to OTLP receiver: java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
	at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:547)
	at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602)
	at java.base/java.net.Socket.connect(Socket.java:633)

and the root cause is traced by the test logs:

...
otel-collector> Error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):
otel-collector> 
otel-collector> error decoding 'exporters': the logging exporter has been deprecated, use the debug exporter instead
otel-collector> 2024/10/30 09:04:22 collector server run finished with error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):
otel-collector> 
otel-collector> error decoding 'exporters': the logging exporter has been deprecated, use the debug exporter instead
...

which leads to the OTel collector configuration file, currently set as:

...
exporters:
  logging:
    verbosity: detailed
...

The solution is described here: open-telemetry/opentelemetry-collector#11337 (comment), although we might want to freeze the OTel collector image version to align with the one used by the WildFly test suite.