is_first_decorator can be flaky

[felixnext]

When many decorators are used in parallel (in unittests for example) the is_first_decorator system can be flaky (maybe due to collisions in the id(func) space?).

This forced to enable the removal of variable keyword parameters to all function signatures in BaseDecorator. This is not ideal and should be fixed! (In that case shield the variable keyword removal again for only the function in is_first_decorator.

Note that this adjustment has to happen after the __increase_count call in line 199:

python-functown/functown/utils/base_decorator.py

Line 199 in 75617ec

self.__increase_count(id(self.func), id(execute))

[felixnext]

This is reduced with #10 - Reason was non safe multithreadedness

This can still happen in Unit-Tests that are parameterized (since they access the same underlying function that is decorated, therefore generating the same base id. Therefore all unit tests are now executed with --forked command to ensure isolation!