Remove Circular Dependency to Quarkiverse

[radcortez]

Describe the bug

In https://github.com/quarkusio/quarkus/pull/44079, we discovered a couple of integration tests that rely on Quarkiverse extensions, which broke due to the changes of that PR:

In Observability LGTM with io.quarkiverse.micrometer.registry

• https://github.com/quarkusio/quarkus/blob/10c335d2dde67a58d2fff4155de9ce62a130b55c/integration-tests/observability-lgtm/pom.xml#L26-L30

In Virtual Threads - JMS with io.quarkiverse.artemis

• https://github.com/quarkusio/quarkus/blob/9fd098a84cf4f8ce1e717ebd9eb6551adc94732a/integration-tests/virtual-threads/jms-virtual-threads/pom.xml#L16-L26

These must be replaced by core dependencies or moved somewhere else out of the core.

[quarkus-bot[bot]]

/cc @brunobat (micrometer), @cescoffier (virtual-threads), @ebullient (metrics,micrometer), @jmartisk (metrics), @ozangunalp (virtual-threads)

[brunobat]

In theory,

 <dependency> 
     <groupId>io.quarkiverse.micrometer.registry</groupId> 
     <artifactId>quarkus-micrometer-registry-otlp</artifactId> 
     <version>3.2.4</version> 
 </dependency> 

Can now be replaced by the default prometheus registry with no impact because we now have a scraper in the dev service. CC @alesj