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.

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

buidler: Add tmp fix/workaround on movement order

builder: Use periodicity to determinate start date

builder mixin: Take into account supply date range before create movement

builder: Hackish immediate reindex of order to work for parallel build

builder: use dedicated script to evaluate min stock

builder: autoPlan only if possible

builder: Reference of order line is reference of resource line

builder: include order delay and effective date

builder: fixup add missing part for effective date

builder: Tweak and fix supply builder

builder: Fixup supply builder

builder: immediate reindex delivery on creation

builder: use _edit on delivery to only reindex modification

builder: Supply builder work with period

builder: Supply builder improved

builder: use flow unit for min stock calculation

builder:  Supply Builder Fix future inventory for parts not activated yet

builder: Supply builder do not create movement for resources that won't be consumed in the future

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

See merge request !2046

See merge request !2055

we mainly add a Quality Assurance Module, which mainly contains: Quality Control, Gate, Traceability, SMON, ACOM

Quality Control: Present a quality control, such as validate document
Gate: when a gate is posted, the quality element which's int index is greater than this one and smaller than next gate will change to Expected state
Traceability: used to record the informations of products used
SMON: it's like a Gate, when validate, the product is off of fabrication line
ACOM: all controls are finished, manufacturing execution is finished

The Quality Element has a Quality Assurance Workflow workflow described as blow
Draft -> Creation State
Queued -> Document is planned, wait to show to the user
Expected -> Document is shown to the user for it to be completed
Pending Update -> A version of this document has been posted that doesn't satisfy Quality Assurance. A New version is needed. (useful for Quality Operation that needs to be redone). Document is shown to the user for it to be completed.
Posted -> Document has been completed by the user.
Archived -> A new version of the document has been posted, the old one become archived
it has also a Quality Assurance Interaction Workflow which is used to show next /archive previous  quality element

it's a regression introduced by 1b555dbf

in ManufacturingOrder_view and ManufacturingExecution_view, we have a field Ledger,so probably we miss this category in builder

erp5_site_global_id was from the tiolive time, when we were using ERP5
with mariadb and memcached instances shared by many zope instances, this
was used as a way to implement namespaces in memcached, to prevent
conflicts such as two different zope using the same cache keys.

Nowadays, we no longer share memcached, each ERP5 instance has its own
memcached and this prefixing is no longer needed, but there is still one
exception, when we run test using runTestSuite with --node_quantity
higher than 1, we have multiple running test instances sharing the same
mariadb and the same memcached. In that case, each test instance
uses a different mariadb database, but the risk of conflict remain for
memcached.

To solve this, we introduce a prefix for keys, choosen randomly at test
startup.

This was more or less what the current implementation was trying to do,
but we were setting erp5_site_global_id on the wrong object, so it was
not working since 4889d523 (Define property's default value at class
level., 2012-12-31). Also, this was only done at the level of SharedDict,
but some APIs such as CacheTool or SessionTool use MemcachedDict
directly. There was other problems that using the sql connection string
encoded in base64 was a too long prefix, because memcached are limited
in size. Also it was not preventing collisions when running tests on
the same test node, each runUnitTest execution was still having
pollution from the previous runUnitTest.

This does not validate against the schema:

   Element 'ecriture': Missing child element(s). Expected is ( ligne ).