Writing SQL belongs to catalog.

Improvement: As proposed by Jean-Paul when this extension was added (2010),
allows mixing left- and inner-join lookups.
Improvement: Now it is not required to specify tested_base_category_list
to enable inner joins: they will automatically be used whenever a base
category set on context matches the preference. If all categories set on
context match the preference, then no left join will be used at all.

This only makes a difference when "test=False" is given, which is a hack
anyway.

The main purpose is to stop calling buildSQLSelector so it can be removed.
Remove Base_zSearchRelatedObjectsByCategoryList.
Also, discard a superfluous comment in testArchive which references the
discarded ZSQLMethod, for consistency.
Fixes an existing failure in testArchive.

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.

// 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 nexedi/erp5!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

Due to unproper diff

This reverts commit 2259e304.

* having a "?" before the parameter will allow chromium to encode the search parameter