A lot of configuration parameters are looked up via the ResteasyConfiguration API looked up from the ResteasyContext. We should migrate to using the org.jboss.resteasy.spi.config.Configuration API to take advantage of the MicroProfile Config implementations when it's available.

On the server side using the ResteasyConfiguration generally works okay because there is a ResteasyContext available. On the client side this is less likely to be used and generally requires the system property to be set. Ideally we could get the property from the client Jakarta REST Configuration too, e.g. ClientBuilder.newBuilder().property("resteasy.preferJacksonOverJsonB", true).build().

This needs to be analyzed first to see what kind of impact it may have.