Drop overly descriptive comments.
Simplify code.
Fix coding style.

Backward compatibility was not implemented everywhere, and it is masking
bugs: not all parameters were provided to these ZSQLMethods, which can
cause all sorts of bugs and performance issues because of DTML defaulting
to acquisition context for missing arguments. Drop this overcomplex code.

by adding Base_downloadWithCors that acts like Base_download but
adds CORS headers according to Base_prepareCorsResponse.

By using Event_generateReference from erp5_crm

/reviewed-on nexedi/erp5!214

Allows accessing any catalog column after parent relation, instead of only
pre-configured columns.
Allows reverse relation lookup (for the non-parent part of the relation,
as child relationship is not supported).
Also, drop now-redundant related keys.

Simplifies extension.
Also, factorise constants a bit.

Change autocomplete from Ctrl-Space to Alt-Space, because
the former is already used for switching keyboard language.

Change indent less from Ctrl-] to Shift-Tab, because the
former is already used for switching between browser tabs.

@nexedi any objections ?

/reviewed-on nexedi/erp5!213

Including all external method arguments in the error is needlessly
verbose.
If you rely on this to debug, define this inside your external method.

Otherwise, longer results would be truncated and shorter results would
produce activities with an empty list as argument.

/reviewed-on !210

/reviewed-on nexedi/erp5!206

editable state is kept

Mimic formulator behaviour to reduce jIO conflicts.

When AdoptSolver is called for the property 'quantity' on a list of
simulation movements having sum([simulation quantities]) equal to 0,
then the delivery error must be 0.

Before, we were setting as delivery error -quantity of that simulation
movement, then we still had divergence even after the solver was called.

ERP5JS will display the worklist on the search page in such case.

On workflows accounting_date_workflow and counter_date_workflow, the permission name was
using capitalized case instead.

This allow to separate management of click/blur events.
Blur is only used to remove the li elements.
Click check if user selected a li element.

After going to a resource that you are unauthorized to view, then the error is shown incorrectly because the default UI tries to use properties of the same resource, reraising unauthorized error.

With this commit, if unauthorized is reraised, it tries to show the error from the portal object. If the user is still unauthorized to see the error output, then the error is shown directly without the classic UI.

/reviewed-on nexedi/erp5!192

Apply security in ERP5User methods.

Require the findings to be consistent when applicable.
May happen for example when migrating a user from being handled by one PAS
plugin to another.

It does not depend on a specific plugin.
Also, update all importers.
Also, reduce import cycles in ERP5Security.

The value used to be displayed will be the last value of the tuple