newTemp*() deprecation (1bce8563, 04b49859): Remove hack in NotificationTool.sendMessage() not working with ZODB Components.

When a Portal Type could not be found, sendMessage() was creating a temp_object
instead (even when passing store_as_event=True) by calling newTempPORTAL_TYPE()
and thus assuming a filesystem Document. So from now on, Portal Type must be
available and thus sendMessage() will fail otherwise. Moreover, if store_as_event
is True, this will no longer create a temp_object silently as it used to when
the Portal Type is not available.

This moves Mail Message Portal Type from erp5_crm to erp5_base as MailMessage_send
(send() being called directly from sendMessage() for temp_object) is already
in erp5_base. As this is only to allow creating temp_object, leave its Actions,
Workflows and Constraint relying on erp5_crm API as they are.

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

This portal type is defined in erp5_trade, and the allowed content type in
Delivery Builder is defined in erp5_trade, only the allowed content type we
defined in erp5_base, which is incorrect, because it makes erp5_trade
allow some non existing types in Order Builder.

Fix this by moving the allowed content type in erp5_trade.

- fix indentation
- make overloaded methods accept same arguments as on parent class
- use list comprehension instead of map()

PDM has some scripts, such as Consumption_asCellRange, it seems
consumption is a generic concept that should be in pdm, not in apparel.

erp5_pdm does not depend on erp5_trade, so it cannot use proxy fields
from erp5_trade

This business template uses proxy fields from erp5_trade

These scripts are used in coding style tests, but because it was in
erp5_administration, all coding style tests had to install
erp5_administration and all its dependencies. Which is against one idea
of the coding style test, which is supposed to check that business
templates declare their dependencies correctly, but if we install all
business templates that erp5_administration depends on, the test might
have false positives of missing dependencies.

Since 7b4a3d4c instead of subscribing after add code unsubscribed which is illogical. Revert back. Credit Kaz.

Tests passing : https://nexedi.erp5.net/test_result_module/20200327-660269E/view?ignore_layout:int=1

See merge request !1092

This is already defined in erp5_simulation, also Solver Type does not
exist in erp5_base

testUpgradeInstanceWithOldDataFs: New Unit Test to check upgrade of old instance to current ERP5 version.

After copying old instance ZODB and SQL from erp5-bin.git, this checks whether
instance can be successfully through upgrader. Introduced because of 140be41d.

Since 7b4a3d4c instead of subscribing after add code unsubscribed which is illogical. Revert back. Credit Kaz.

See merge request !1085