This is useless and likely to trigger errors anyway, such as the document
being not available when Interactions is actually called.

The former calls zope.i18n.translate() which calls MessageCatalog.translate()
by passing 'default' argument to the original message, thus returning the
original message when there is no translation. But, when the latter is called
without 'default' argument, it is set to message.strip(), thus returning the
strip'ed original message.

Before, Constraints on the filesystem were checked but this does not work in
the forementioned case as the Constraints of project A are not available
anymore, thus those Constraints were skipped.

When installing many bt5, many activities are generated which may take a very
long time to process, instead process them bt5 per bt5 to avoid such issue.

When starting a node, ERP5Site.__of__ calls ComponentTool.reset(), which was
never synchronised so it returned True (without generating a new cookie at its
level) and causing synchronizeDynamicModules to be called with
force=True. This generated a new cookie and leading to dynamic classes being
meaninglessly regenerated on all nodes.

Instead, modify ComponentTool.reset() behavior so it *always* reset Portal
Type classes when Components are reset (as it should have always been as the
class inheritance may have been modified) and force regeneration of Portal
Type classes in this method if reset is True.

Signed-off: Vincent Pelletier <vincent@nexedi.com>

generateNewId() calling getIdGenerator() accessor which not available yet,
thus define a dummy accessor so that erp5_property_sheets can be installed.

This avoids copying/pasting the content of the form and also keep records for
later inspection.

Avoid running out of file descriptors when backing up many objects in the trash upon bt5 installation.

Before, when installing a bt5 whose format has changed, many subobjects may
end up being backup up, but it keeps one FD per subobject, thus easily
reaching the limit of 1024 FDs (as given by ulimit -Sn/-Hn).

This is a followup of b71e5a73 specific to TrashTool as that commit seems to
only fix the issue when TrashTool is not used.

Upon Business Path Item installation, update Local Roles of objects whose Portal Types defines Roles.

Before, Local Roles were not updated upon Path Item installation, thus leading
to security issues (such as Trade Model Line). This avoids ugly hacks in
Upgrader and in tests as well.

To show a workflow dialog which absolutely fail is not good.

Improve error handling on Workflow_statusModify. If divergence is solved by other user, then show a nice message.

Uid must be always consistent. If uid is changed, then workflow action which user selected is applied to different workflow and it causes different result.

Improve error handling on Workflow_statusModify. If requested transition is not available, then show a nice message.

PasswordTool_viewResetPassword/text_content from erp5_core wrongly requires
Field Library in erp5_web and EmbeddedFile_view/my_description from erp5_base
wrongly requires Field Library in erp5_dms.

If an user has set SVN working copies in its preferences, it cannot be
modified anymore after upgrade.

Now both ascending arrow and descending arrow are displayed in title column
and user can sort in specific order explicitly. User also can sort multiple
columns by click without using sort-on-dialog.

Fix error message of StringAttributeMatch Constraint incorrectly renamed after migration to ZODB (78e2ae32).