A new column ledger in the stock table and some related keys
(stored in erp5_mysql_innodb_catalog) have also been created
Adds tests for inventory queries based on ledger in testInventoryAPI

erp5_core: changes portal type filter on dynamic_class_generation_interaction_workflow and base_type_interaction_workflow to a portal group filter

These workflows now apply on every type belonging to the grouping type 'type_definition': Base Type and other portal types of portal types

ERP5Type: introduces 'type_definition', a grouping type to identify portal types defining other types

ie: Base Type and portal types of portal types

erp5_accounting,erp5_project,erp5_payroll,erp5_trade,erp5_open_trade: changes base type of Deliveries to Delivery Type

: Orders and Packing Lists portal types now have Delivery Type as portal type

For the moment it only allows to define a list of ledgers
on the portal types inheriting from it, to create a filtered
list of ledgers allowed on the final objects.
Adds DeliveryType.py, a new Base Type for Delivery portal types
Adds testTypeDefinition.py, a new suite to test DeliveryType

_viewAccountingTransactionList forms can filter on preferred ledgers.
Preferred Ledgers can be set in preferences.
Form fields related to ledgers are not intrusive and don't display if None is defined.

Which was related to an older version of the simulation

With complex security scripts to calculate user groups,
calling getPreferredArchive() from DA.__call__ still causes
"maximum recursion depth exceeded" errors when caches are empty.

In order to address the issue, we must review erp5_archive. Instead of that,
this commit first checks whether the archive tool is installed, which is anyway
faster that getting a preference. An expected failing test is also added.

- normalize path to avoid to traverse with wrong value
- review KeyError message when domain is unknown
- use getWebSiteValue when possible

/reviewed-on !124

Dependency should be defined directly on bt5 if needed.

'keep_existing' argument of Base._edit has never been used
and we should consider removing it.

When defining a guard on an object, calling
a method such as Base_viewDict on that object
could be denied due to guard acquisition.

- the check is moved to a less performance-critical place
- getPortalObject was forgotten in commit d8e9ed19

- 'apply' causes a break in cProfile results
- 'apply' is deprecated (removed in Python 3)

* reference
* translated_title
* the usual owner_title, creation_date and modification_date
* remove useless listbox_editable_fields that are defined in the field library

This business template does not seem to follow the guideline yet

For example, Python Scripts were:
- dirty in the imported BT (causing all of them to be reinstalled on upgrade)
- compiled to return None