On python2, attributes of new style classes (classes, not instances)
were not properly validated. On python3, attributes of classes were not.

In current versions, sorted is allowed in RestrictedPython.

Also, our implementation of sorted was not correct with generators,
it consumed the generator by iterating on it a first time to check the
values.

Run zope with ERP5_COMPONENT_OVERRIDE_PATH set to a : separated list of
path containing components files to load components from files instead
of portal_components.

This can be used to repair zope after a bad edit of component.

This scenario does not really seem important, in such a scenario, first
repair the broken class (typicallly, by fixing the business template
dependency so that the business template containing the broken class is
updated first)

for pylint 3 to understand erp5 dynamic modules

false positive from base classes are propagated in any class inheriting
from Folder of Base. Disabling is more practical because duplicate-bases
errors are not common.

If preferences are not set, this causes a non existant style to be used

On recent pylint, this is flagged as unnecessary-pass

Also update the link that was pointing to python2 doc

We want these columns to be "binary" so that mariadbd compares them
without any collation, but we don't want to use binary type, because on
python 3 the brain attributes are bytes (user ids are strings everywhere
else).

This also normalize the same columns present in worklist cache table.