Allow user to reuse the same cropper area in a session.

It is unexpected that the scanner device is untouched between multiple scan sessions.

Limit the media height.

Patch cropperjs to force it rendering when resizing the window.

Use the GPU to speed up the image manipulation process.

Reduce the number of pixel managed by caman

Display the capture screen as fast as possible

Like when the browser is offline.

newTemp*() deprecation (1bce8563, 04b49859): Add DeprecationWarning when calling a newTemp*() function.

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.