We need to be able to see the future without auto planned orders, else how are we going to update them?

erp5_mrp: Copy price_currency to Manufacturing Execution and Production Packing List (PSA specific?).

In PSA for ME: Problem Report is created from a ME which then build a Returned
IPL from scratch copying properties from the ME. After this Returned IPL is
root-expanded, Real Time Inventory Accounting Rule is expanded too and requires
price_currency.

This also avoids KeyError exceptions when Activities have already been processed
in the meantime.

In contrary to the ParentDeliveryPropertyMovementGroup for property, it has
never actually checked the parent Delivery but the current one.

erp5_accounting_l10n_fr: Allow to pass additional Catalog parameters to select Accounting Transaction to FEC export.

Introduced for customer Unit Tests to be able to FEC export only ATs of the
current Unit Test FEC based on 'title'.

erp5_real_time_inventory_accounting: Accounting Transaction state should be 'Posted to General Ledger' (stopped), not draft.

erp5_accounting_l10_fr: FEC: Allow to specify from_date instead of using the last Accounting Period.

For instance to build FEC reports on a daily basis.

erp5_accounting_l10n_fr: 'at_date' in FEC Dialog requires month/day so these should be in the generated filename too.

erp5_accounting_l10n_fr: FEC Report: Allow to group by ledger or ledger+portal_type in addition as per portal_type (the default).

This required refactoring the source files as the implementation was
portal_type-centric. This adds a dedicated Python Script with ProxyRole=Manager
to create Active Processes and thus avoid executing code as Manager as much as
possible.

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.