The issue is occured when using inventory document with inventory cache.
Add a test case to make sure this issue has been solved:
  testInventory#test_18_InventoryDocumentAndInventoryCache.

Replace a zsqlmethod for translated_simulation_state_title with python script to add an extra condition to where expression. This helps m
ysql optimizer to make a better plan. Without it mysql optimizer may make a bad plan to join catalog and translation and causes bad performa
nce problem.

This reverts commit 70a8e561 because this
changes is about improving the performances of Accounting Transaction Module
not used in this project. Moreover, this change would required to reindex
Accounting Transaction Module.

Conflicts:
	bt5/erp5_configurator_standard/bt/revision

Use IPAexGothic to make sure that Japanese is displayed properly. Also, make
sure that all the files are properly closed even if an exception occurs thanks
to 'with' and 'NamedTemporaryFile'.

Fix an inventory bug. When there are more than 300 inventories which are cancelled by inventory document, inventory document creates wrong stock records.

Fix incorrect change of my_view_mode_quantity ProxyField which must point to Base_viewFieldLibrary/my_view_mode_quantity so that figure CSS class is applied (9fcbe9c1).

To apply this change on existing on existing table:
ALTER TABLE stock MODIFY order_id BIGINT UNSIGNED

Before, when creating new full inventory Document, resources which are not
present in new Inventory Document were simply ignored. So, new movements were
added "manually" with quantity less than or equal to 0 to workaround this
issue.

New inventory fixes this issue so that this workaround is not needed
anymore. Temporary movements are created for resources not present in new
Inventory Document and added to stock table (through z_catalog_stock_list Z
SQL Method) with uid equals to Inventory Document UID.  However, the primary
key on stock table is (uid BIGINT UNSIGNED, order_id TINYINT UNSIGNED), thus
when there are strictly more than 255 temporary movements, order_id overflows
because the max value of TINYINT UNSIGNED is 255 and MySQL sets order_id to
255 after the first 255 temporary movements (as strict SQL mode is not
enabled), thus raising an IntegrityError later on because of duplicated
entries.

erp5_simulation should not be required for erp5_trade and erp5_accounting as some system do not use simulation.

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 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.

Also, move Portal Types Role installation before Path so that they can be used
before updating Roles during Path installation.

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.