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.

- Allow superuser to get RSS ;
- Remove useless portal_skin=RSS paremeter.