Less ambiguous than previous syntax while keeping names short.
Allows defining more flags without limiting base_category namespace: the
only forbidden base_category id is "related", which was already reserved
(ie, not working) in previous syntax.

These improvements include :
   * better address reporting
   * better handling of Social Security Number and Temporary Technical Number
     for foreign employees
   * add more checks and UI error messages to report wrong values to the user
     before he submits the DSN
   * fix bugs for some edge cases

When aggregating Paysheets using a dialog, we don't want to aggregate deleted ones.

* Only process Expense records with a date set (avoid processing records with no data)
* Add garbage collect on empty draft records
* Change jIO configuration to resolve conflict with remote as the reference
* Comment indexxedDB patch XXX code should be added for Safari to use websqlstorage

// XXX Please note this is a work-around to have a usable application
// waiting for a bug in IndexedDB or jIO to be fixed
// this bug can been seen on 'fast' devices where
// data stored in settings is not accessible right after save.
// it was shown that after redirecting to sync page, the
// "sync_reload" value got in the sync gadget was "undefined"
// Hence triggering synchronization and not setting the storage first
// and redirecting once again on the jio configuration page

Revert "[erp5_ui_test] Be always explicit (with sorting) and bugfix fr argumentto FooModule_createObjects

This reverts commit 1bb79a39

/reviewed-on nexedi/erp5!332

/reviewed-on !329

Entities can be given identifiers by other organisations when they suscribe to their service. This identifier can be seen as a contact, as it will be used to reference the entity in all further exchanges. As the number of suscription can be unlimited, creating a new property for each kind of identifier becomes heavy, but customizing contacts using getIdTranslationDict is easy.

As a real life use case, in UK, a company which is allowed to instruct direct debits to their customer bank accounts is given a Service User Number, which should be transmitted with all direct debit instructions.

/reviewed-on nexedi/erp5!316