Calling these can break catalog by not caring about concurrent indexation
activities. Even non-restricted code should not call these, but:
- they cannot be reliably renamed, as there exist activity dependencies
  looking for these exact names (which is a bad practice on its own)
- there is no simple access control mechanism for non-restricted code
So rely on developer discipline instead.

Also, simplify scripts while doing so.

These methods must not be called synchronously:
- they can break catalog by not being careful enough about other
  reindexations which may happen in parallel. See the serialization_tag
  mechanism for more.
- indexation gets executed in the security context of the user causing the
  call, which may lead to an indexation result different from what happens
  when indexation happens with an all-accesses user.

To remove the need to directly call immediate reindexation methods,
allowing to prevent further misuses of these.

Do not check portal's isIndexable, it is checked again in ZSQLCatalog.
Directly bind superclass callable instead of doing an extra getattr +
call.
Trivial python simplifications.
Assorted coding style improvements.
Drop unhelpful comments and docstrings.

getSecurityQuery returns None when caller is superuser. Avoid passing it
to buildSQLQuery, as it would mistake security_query for a column name.

Float fields are needed to round amounts.
Also, discard empty form groups.
Also, make "hidden" the first group, so any created field gets hidden by default
(which is what we want for all listbox "editable" fields).
Also, remove overrides which seem unneeded for report appearance:
- "lines" is not used for OD* rendering
- "columns" is already the same as in original field
"editable_columns" is used in odt (and maybe in ods, unclear), but
inconsistently with its intended use... so leave it, sadly.

Fixes bug /#/bug_module/20171211-153B610

/reviewed-on nexedi/erp5!526

Removed code from not implemented and not needed compatibility layer.

/reviewed-on nexedi/erp5!525

/reviewed-on nexedi/erp5!527

Display it on one line

command: display_with_history

See nexedi/erp5@be501468

It cause huge timeout in automated tests, issue with dispatcher

[portal_property_sheets/SupplyLine, erp5_pdm] Add ledger category to Supplies and Supply Lines. And allow users to set an optional quantity unit category to Supply Lines. Also add matrixbox view forms for max delay, min delay, max flow, min flow, max stock, min stock properties.

Fixes /#/bug_module/20171208-5E8D43

/reviewed-on nexedi/erp5!523

Allows overriding it on instances where the invariant
  grouping_reference IS NULL == grouping_date IS NULL
is applicable, allowing simpler query execution plans.

For type checking (not recommended, but sometimes useful).
Expose it as BaseQuery, to avoid conflict with AutoQuery original name.

Make it more easily extensible by exposing a callback.
Stop loading documents in the simple version that are only needed by the
detailed version. Also, stop checking for this inside the main loop, and
instead use the callback mechanism.
Use a single query to look for mirror section title instead of one per
mirror section.
Behaviour change: mirror section (ie, the entity) title is not
translated anymore. It used to be because there did not seem to be a
reasion not to. It is not anymore to avoid loading rach entity from ZODB
in the default report. This rework makes customisation easier, including
overwriting this untranslated title with any desired transformation.

/reviewed-on nexedi/erp5!521

[erp5_xhtml_style] erp5.css: Set a margin between Save button and the block of tabs, then Save button does not overlap with tabs.

This allow to go to dialog page on a module, and keep the search parameter.

SearchField: keep the last full text parameter editable
Allow to focus on a specific input
Searchfield: use an hidden field to store the parsed value (to simplify test code)
Display full text queries as much as possible in raw format

This will prevent the input gadget to be changed if its parent call render with the same value (as ERP5 does in case of formulator error).

The typical use case is to go to a module from a worklist link.
This leads to a complex query to display only the matching documents.

Opening the filter panel should not lead to lose the query.
User must be able to add extra parameters to this query thanks to the filter panel.

This was done by:
* changing the DOM only in the changeState method
* handling unexpected search expression (not parsable, complex one, unknown column, ...)
* improving query operator support
* dropping not needed HTML element attributes.
* adding tests

/reviewed-on nexedi/erp5!520

fixing a bug in firefox 57 that prevented to click on links

- ERP5Site_getScalabilityTestMetric script gets metrics of last created objects
- Bootstrap script now creates the users for test

/reviewed-on nexedi/erp5!513