MessageBodyReader/Writer matching doesn't work properly with CDI beans

When a `MessageBodyReader` or `MessageBodyWriter` is defined as a CDI `@ApplicationScoped` bean, it is wrapped by the proxy.

This causes `org.glassfish.jersey.message.AbstractEntityProviderModel#getProviderClassParam` call to fail to get the provided Java type from the generic type argument from the provider instance (the class returned is the class of the proxy object, not the class of the actual provider implementation), which ultimately results in `Object.class` being returned to the caller.

This can make custom MBR/MBW "further away" if there are multiple providers for a given type, and prevent it from ever being used.

Start at org.glassfish.jersey.message.AbstractEntityProviderModel#getProviderClassParam, which the issue identifies as returning Object.class for CDI-proxied providers. Trace how MessageBodyReader and MessageBodyWriter provider classes are inspected, then verify that the actual generic Java type is recovered and provider matching no longer ranks custom CDI beans incorrectly.

Written by the indexing model from the issue text.