fix(OSGI) Rest plugin fails when redeployed from OSGI Refs: #31348

[fabrizzio-dotCMS]

Fixed IllegalStateException: object is not an instance of declaring class that occurs when OSGi bundles are unloaded and reloaded in Jersey REST endpoints.
Root Cause: Jersey's default ResourceMethodInvocationHandlerFactory uses a static DEFAULT_HANDLER that captures method references from the initial ClassLoader. When OSGi bundles are reloaded:

Method objects retain references to the original ClassLoader (A)
Target instances are created with the new ClassLoader (B)
method.invoke(target, args) fails because target is not an instance of the method's declaring class from different ClassLoader

Solution
Implemented a proactive ClassLoader resolution strategy by replacing Jersey's default InvocationHandler:

Custom ResourceMethodInvocationHandlerProvider (DotResourceMethodInvocationHandlerProvider)

Registered with @priority(1) to override Jersey's default handler
Implements proactive ClassLoader conflict detection and resolution

Proactive ClassLoader Resolution

BEFORE method invocation, checks if target.getClass().getClassLoader() differs from method.getDeclaringClass().getClassLoader()
If different, resolves the correct method from target's ClassLoader using target.getClass().getMethod()
GUARANTEES method and target share the same ClassLoader before invocation

Enhanced Error Handling

Downgrades original Jersey exception logging from SEVERE to WARN level
Removes verbose stack traces to reduce log noise
Provides clear diagnostic messages for ClassLoader conflicts

Testing
Verified fix resolves the original IllegalStateException during OSGi bundle reload cycles without impacting normal REST endpoint functionality.

This PR fixes: #31348