"java.lang.ClassNotFoundException: com.isomorphic.hibernate.HibernateDataSource" in logs after updating to 13.1

[Crack]

After updating my project from SmartClient 13.0 to 13.1 (v13.1p_2025-05-12/PowerEdition) I have this warning in my logs:

13:38:24.867 WARN [admin][web-52] com.isomorphic.interfaces.InterfaceProvider : Configuration error - cannot find provider for interface: IHibernateDataSource

java.lang.ClassNotFoundException: com.isomorphic.hibernate.HibernateDataSource
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
    at java.base/java.lang.Class.forName0(Native Method)
    at java.base/java.lang.Class.forName(Class.java:375)
    at com.isomorphic.base.Reflection._classForName(Reflection.java:332)
    at com.isomorphic.base.Reflection.classForName(Reflection.java:296)
    at com.isomorphic.interfaces.InterfaceProvider.exists(InterfaceProvider.java:159)
    at com.isomorphic.interfaces.InterfaceProvider.exists(InterfaceProvider.java:138)
    at com.isomorphic.sql.SQLConnectionManager.<clinit>(SQLConnectionManager.java:85)
    at com.isomorphic.sql.SQLDriver.getTransformedResults(SQLDriver.java:1198)
    at com.isomorphic.sql.SQLDriver.executeQuery(SQLDriver.java:1739)
    at com.isomorphic.sql.SQLDataSource.executeNativeQuery(SQLDataSource.java:674)
    at com.isomorphic.sql.SQLDataSource.executeNativeQuery(SQLDataSource.java:668)
    at com.isomorphic.sql.SQLDataSource.SQLExecute(SQLDataSource.java:1998)
    at com.isomorphic.sql.SQLDataSource.SQLExecute(SQLDataSource.java:1808)
    at com.isomorphic.sql.SQLDataSource.processRequest(SQLDataSource.java:509)
    at com.isomorphic.sql.SQLDataSource.executeFetch(SQLDataSource.java:453)
    ...

isomorphic_hibernate dependency is not present in my project because I'm not using Hibernate datasources in SmartClient, so this warning shouldn't be show. I would expect, at most, a INFO log telling me that Hibernate integration is not available, not a WARN with stacktrace.

[Isomorphic]

Yeah, this was an unintended consequence of of a task we did to rationalize exception handling across the framework, and we agree that it is too much. Affected builds as of tomorrow will suppress that log in favor of a more low-key one