FullMicroprofile ported to new tracing API, MP6+ Q3.6+

[Karm]

Fixes #225

$ mvn clean verify -Ptestsuite 
-Dtest=RuntimesSmokeTest#quarkusFullMicroProfile,DebugSymbolsTest#debugSymbolsQuarkus,PerfCheckTest#testQuarkusFullMicroProfile 
-Dquarkus.native.builder-image=quay.io/quarkus/ubi-quarkus-mandrel-builder-image:jdk-21 
-DincludeTags=runtimes,reproducers,perfcheck -Dquarkus.version=3.6.0 | tee log.log 

passes now.

[zakkak]

We need to make these Quarkus/Mandrel specific.

My understanding is that you are increasing the threshold for Quarkus 3.6, but this will make us miss increases happening in 3.2 for instance.

[jerboaa]

+1

[Karm]

@zakkak Yes. The increase is caused by OpenTelemetry being a much bigger library than OpenTracing apparently.

The "design" of the property files did not take into account the Q versions.

We can start having some per-quarkus-version property files. Perhaps per Mandrel major.minor too.

Non-quarkus apps would have just the Mandrel major.minor?

Wondering how to make it nice and tidy without inflating the logic too much.

[zakkak]

Non-quarkus apps would have just the Mandrel major.minor?

Yes

Wondering how to make it nice and tidy without inflating the logic too much.

I need something similar in quarkusio/quarkus#36108 and I was thinking about using a directory structure like <quarkus-version>/<mandrel-version>/threshold.properties. WDYT?

[zakkak]

LGTM other than the threshold bumps which we should better address in another PR since it's a general issue not specific to this PR.

[jerboaa]

I'm fine with getting this in and do the proper threshold refactoring fix in a follow-up.