Like when the browser is offline.

This reverts commit 527d688e.

This prevent getting DB read/write conflicts

Do not access form submission REQUEST from the listbox list method,
as it is rendered asynchronously in ERP5JS

This reverts commit 35b2c024.

Allow edition in the new UI

This make everything slow as hell and prevent to quickly save.

This moves portal_solver_processes from erp5_base to erp5_simulation as its
Portal Type definition is already there and it was initially moved away from
erp5_simulation presumably because erp5_simulation was for new Simulation at
that time.

Also, as delivery_causality_workflow uses portal_solver_processes, move it to
erp5_simulation (along with delivery_causality_interaction). This required
fixing Unit Tests to install erp5_simulation before erp5_trade (it already
depended on it anyway).

When migrating `Immobilisation` Document, imports of not yet migrated
ImmobilisationMovement Document were also replaced...

testUpgradeInstanceWithOldDataFs: Check that all Portal Types classes can be loaded successfully after running upgrader.

testUpgradeInstanceWithOldDataFs: Old Data.fs was created with `--portal_id=erp5`, so it should be passed for erp5testnode too.

ZODB Components: Migration dialog: Only consider Portal Type Document/Tool class and not all its subclasses.

This makes it easier to migrate only Document/Tool classes to the current bt5,
considering that subclasses below are likely to be used in several places.

These conditions were added many years ago and they should not be needed
since checkboxes work without this extra complexity

Move `BusinessTemplate_getPythonSourceCodeMessageList` to `erp5_core`, so that coding style tests don't need to install `erp5_administration` and all its dependencies.

`erp5_core` is not the final place for this, because this is not required to for business template bootstrap, but this is temporary until we finish business template reorganisation.

This revealed several problems of wrong dependencies between business templates that we could not see before, when coding style was installing too many business templates such as `erp5_pdm`, `erp5_trade`, `erp5_simulation`, `erp5_project`.

See merge request !1089

ZODB Components: Interface Component: pylint was incorrectly emitting: `W: __init__ method from base class is not called`.

now BusinessTemplate_getPythonSourceCodeMessageList is in erp5_core

ZODB Components: Ignore low-level TypeProvider (TypesTool and SolverTool) classes in FS migration Dialog.

This is a script from erp5_core, but Inventory Module is a portal type
from erp5_trade.

Component is not a valid prefix for python components from
portal_components, it's the name of a resource class from erp5_pdm.
ComponentMixin is the valid prefix.

This scripts are used only in code mirror integration

This busines template has actions using forms from erp5_simulation, for
example Rule_view on Payment Simulation Rule