This allows code of movement group to still works when they use
setter/getters defined by property sheets

Fully rewrite portal_simulation.mergeDeliveryList to use builders to reconstruct new
merged delivery.

Add parameter "merge_delivery" to builder. This parameter is used when
merge should be done in such a way that movement group at delivery
level are ignored

The pagination was not working when using the limit parameter, and when
the total number of documents is equal to the pagination limit + 1.

user should use solve divergence for split and defer

related to current sm

erp5_accounting: make section editable in listbox and has same possible value as Transaction's section

We might get variation from a transformation on a delivery line, which is not good

In the case of manufacturing, we would like to define a "use" category on delivery, and we would
to get it on lines to allow searching predicates

This avoid issues when expanding simulation. Indeed, we have cases with temporary production
order line generated by composition, and then search of predicate fails on such movement (because
we try to call getAcquiredCategoryList and this try to check if there is sub objects, like default_address,
and then it complains that composition should never be used has folder !)

Since predicate could match any property, the transformation corresponding to a line might
change upon the change of any property. Make sure the interaction take into account any property

Let's use reference_date_method_id on Trade Model Paths.

* Code clean up
* Remove hardcoded ledger to pick date
* Add code to defined source section when none is defined

* Fix for special case where purchase packing list is root.