feat(trait): Migrate prometheus trait from microprofile metrics to micrometer

[gansheer]

Fixes #1773

Motivation

In Quarkus 3 / Camel 4, microprofile-metrics will be removed, and micrometer extension is its replacement.
The prometheus trait need to be modified to use the micrometer extension.

Description

The micrometer extension replaces the microprofile extension, with the additional prometheus registry.
The e2e existing test is updated to be the most similar as possible in terms of metrics tested, but since micrometer offers less possibilities there are some adaptations.

Release Note

Migrate prometheus trait from microprofile metrics to micrometer

[gansheer]

The PR is in draft until I manage to fix the e2e test.

[gansheer]

I am trying to see if it is possible to add in the prometheus trait code the addition of a builder property quarkus.micrometer.export.json.enabled=true to ensure json api is available by default. I haven't manage to. Is there a way to do it while acting on the e *Environment object ?

[squakez]

I think this is another case where we need to understand how to implement a trait leaving implementation details about runtime outside of Camel K: #4166

[gansheer]

I think this is another case where we need to understand how to implement a trait leaving implementation details about runtime outside of Camel K: #4166

I see, I will exclude it from the idea from this issue and add how to activate JSON's API it in the documentation's example for now.

[squakez]

Thanks!