JavaUseProvider might attempt to instantiate interfaces or abstract classes

If you have a data-sly-use which receives a FQN of an interface or abstract class, the Java Use provider will not make any checks and will try to instantiate it anyway, causing a java.lang.NoSuchMethodException com.example.InterfaceName.<init>().

This is a problem when your code base normally relies in an adapter factory to get implementation of an interface and the adaptTo returns null, causing sightly to try the java Use provider

The Java Use provider should not attempt to instantiate blindly classes that it receives.