@component decorator on a class that inherits from another marked with the same breaks its init

[shadeMe]

Describe the bug
Adding the @component to a component class that already derives from another component class with the @component decorator breaks the former's initialization if its __init__ method calls super() or super().__init__.

Error message

TypeError: super(type, obj): obj must be an instance or subtype of type

To Reproduce
Add the decorator to FaithfulnessEvaluator, which derives from LLMEvaluator.

[masci]

This is most likely due to something similar to python-attrs/attrs#1038, the way we reconstruct any decorated component class with new_class would trigger the same problem with method rewriting.

Closest example to our case to reproduce:

from types import new_class
from functools import partial


def copyns(cls, ns):
    """Copy the namespace of the original class"""
    for key, val in dict(cls.__dict__).items():
        ns[key] = val
    return ns


class MyMeta(type):
    pass


class BaseComponent:
    pass


# This is what the `@component` decorator would eventually do
BaseComponent = new_class(  # type:ignore
    BaseComponent.__name__,
    BaseComponent.__bases__,
    {"metaclass": MyMeta},
    partial(copyns, BaseComponent),
)  # type:ignore


class DerivedComponent(BaseComponent):
    def __init__(self):
        super().__init__()


DerivedComponent = new_class(  # type:ignore
    DerivedComponent.__name__,
    DerivedComponent.__bases__,
    {"metaclass": MyMeta},
    partial(copyns, DerivedComponent),
)  # type:ignore

dc = DerivedComponent()  # TypeError: super(type, obj): obj must be an instance or subtype of type

The workaround (that's also mentioned in the linked issue) is to "help" Python understand what's going on calling super() like this:

# ...

class DerivedComponent(BaseComponent):
    def __init__(self):
        super(DerivedComponent, self).__init__()

# ...

dc = DerivedComponent()  # ok

[shadeMe]

Looks like the above workaround is the way forward.