erp5_accounting_l10n_fr: Depend on erp5_deferred_style (FEC Report calls ERP5Site_notifyReportComplete).

ZODB Components not following ID=(document|extension|test).VERSION.REFERENCE convention are not importable anymore.

Import mechanism now relies on this convention to find the document in
portal_components.

This is necessary to get rid of _registry_dict (ZODB Components equivalent of
document_class_registry), along with several locks. This used to be a mapping
between (reference, version) to ID stored outside of Zope Transactions as a
dict on global erp5.component.XXX modules.

This did not work for long transactions such as installing many bt5s:
  1. Transaction1: Install a bt5 with ZODB Component "Foo".
     => Trigger a reset and _registry_dict is cleared.
  2. Transaction2: TimerServer kicks in.
     => Generate _registry_dict without "Foo".
  3. Transaction1: Install another bt5 using "Foo".
     => "Foo" not in _registry_dict and thus considered not present.

erp5_real_time_inventory_accounting: Move Root Delivery Simulation Rule to test bt5 as it is only used in Unit Tests.

erp5_real_time_inventory_accounting: Matching on source_section is not enough (Automatic Delivery Accept Solver).

Also, Alt-Space is already bound to 'just-one-space' and not needed anyway as
CodeMirror binds autocomplete to Alt-/ by default.

This can be chosen through Preference => "User Interface" tab. CodeMirror
default keymap is used by default as until now.

erp5_real_time_inventory_accounting: Split the BP into dedicated ones for Sale, Purchase and Internal.

Checking 'delivery' portal_type for PL type will not work on real
implementations as the PL is not built during the first expand and
expand_related=0 after and this is how it should be done anyway.

Same as IPL use case.

IPL must expand both "In"coming (only PPL until now) and "Out"going (only SPL
until now) SMs, so split up ledger='stock' TMPs and add accordingly two
subcategories to stock ("entree" and "sortie").

Also instead of using 'use' categories everywhere (TMPs and Rules), use the
Delivery Portal Type as this makes things clearer for IPL use case.

This is enough for now to handle both Outgoing/Incoming/Transit use cases.

This implements Outgoing/Incoming Accounting Rules and Builders.

As a matter of fact immediateReindexObject doesn't call reindexObject on the object

SimulationTool: getNextAlertInventoryDate can look for the lowest invetory inferior to the reference quantity

Since last FormBox behavior fix, the context needs to have View permission.
We allow to View for groups that has some permissions on the related delivery.
This way, users that has permission to solve divergences should be able
to get the form, fill it, update it and submit it.

generateMovementListForStockOptimisation was raising error when there was inventories.
The method was assuming that doing getObject() on an inventory line (from
getFutureInventoryList) was always returning a movement. But sometimes we get
the inventory itself. So do not use getVariationCategoryList, but use the variation_text
stored in the stock table.