fix: Do not throw an exception when the solution or entity classes are interfaces

[Christopher-Chianelli]

The superclass of an interface is null. This caused this line of code to throw an exception for solution classes that are interface:

var superclass = bottomClass.getSuperclass();
lineageClassList.addAll(getAllAnnotatedLineageClasses(superclass, annotation));

Since getAllAnnotatedLineageClasses expected superclass to not be null. getAllAnnotatedLineageClasses now returns an empty list for null arguments.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[triceo]

I'm wondering if solutions as interfaces should be supported. What would be the use case? What would be the downsides?

Considering that in all the years we have not seen anyone ask us for this, maybe we don't need this.

[Christopher-Chianelli]

I'm wondering if solutions as interfaces should be supported. What would be the use case? What would be the downsides?

Considering that in all the years we have not seen anyone ask us for this, maybe we don't need this.

It mostly for proxies, which are used in FFI (for instance, when using Python objects in Java via GraalVM).
Proxies almost certainly need a custom solution cloner, but otherwise work without issue.