Make sure the logged process ID is correct in native mode

[geoand]

• Fixes: 'quarkus.log.console.format' '%i' Process ID fixed at build time #39854

[geoand]

@zakkak another instance of the image metrics test causing issues:

2024-04-03T10:22:46.7791862Z 2024-04-03 10:22:46,761 INFO  [io.quarkus] (main) Installed features: [agroal, cdi, hibernate-orm, hibernate-validator, jdbc-h2, jdbc-postgresql, micrometer, narayana-jta, narayana-lra, resteasy, resteasy-client, resteasy-jackson, resteasy-jaxb, resteasy-jsonb, resteasy-mutiny, scheduler, security, security-properties-file, servlet, smallrye-context-propagation, smallrye-fault-tolerance, smallrye-health, smallrye-openapi, swagger-ui, vertx, websockets, websockets-client]
2024-04-03T10:22:46.8258981Z [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.666 s <<< FAILURE! -- in io.quarkus.it.main.ImageMetricsITCase
2024-04-03T10:22:46.8263218Z [ERROR] io.quarkus.it.main.ImageMetricsITCase.verifyImageMetrics -- Time elapsed: 0.002 s <<< FAILURE!
2024-04-03T10:22:46.8265776Z org.opentest4j.AssertionFailedError: Expected analysis_results.classes.jni to be within range [62 +- 1%] but was 63 ==> expected: <true> but was: <false>
2024-04-03T10:22:46.8267631Z 	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
2024-04-03T10:22:46.8269173Z 	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

[dmlloyd]

Hmm I think this indicates at least two bugs. In both the SmallRye and LogManager case, we should use the JDK API to get the PID; we must be caching it. I'll have a look today.

[dmlloyd]

smallrye/smallrye-common#299

[geoand]

💪🏼

[geoand]

Closing this

[dmlloyd]

jboss-logging/jboss-logmanager#464