ProviderBase that copied from Jackson has a bug, need to recopied with the fix

[amiravi]

Jackson had a bug in ProviderBase version 2.19.1. More info about the bug can be found here https://github.com/FasterXML/jackson-jakarta-rs-providers/issues/54
Now Jersey copied ProviderBase class with the bug, and it affects all those upgraded to version 4.x.
To fix need to copy the class from version 2.19.2, which has the fix

[metaxmx]

We are also affected by this bug.
If we use the jersey-media-json-jackson module in our REST-API with Jersey, after some time with parallel requests the nesting of the returned JSON-Objects deteriorates, and too few or too many levels of indentation are rendered.
A backport of the Fix from Jackson (which uses a fresh instance of the (stateful) PrettyPrinter class, and not the same instance) would be appreciated.

In the meantime there seems to be a workaround:
If you configure a custom ObjectMapper used for Jersey Serialization with the following configuration, no default PrettyPrinter will be used, and the Providerbase implementation will construct a new DefaultPrettyPrinter every time:

@Provider
public class ObjectMapperContextResolver implements ContextResolver<ObjectMapper> {

    private static final ObjectMapper OBJECT_MAPPER_DEFAULT = new ObjectMapper()
        .configure(SerializationFeature.INDENT_OUTPUT, true)
        .setDefaultPrettyPrinter(null) // This will force a new DefaultPrettyPrinter for every serialization
        ...

    @Override
    public ObjectMapper getContext(Class<?> type) {
        return OBJECT_MAPPER_DEFAULT;
    }
}

Obviously this is only feasibly if yu don't have any custom settings on the PrettyPrinter which need to be preserved.