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 !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

This contains changes for 2 points:
1. To improve view of ERP5 Catalog and its sub-objects .
2. Export Catalog Methods with no duplication between attributes and properties after migration.

These changes are pointed out  in comment here: !178 (comment 52224)

/reviewed-on !510

BusinessTemplate: Look for string type in property map while extracting Properties for CatalogTemplateMethodItem

After migration of ERP5 Catalog and sub-objects, the filter attributes are
now properties of Catalog Method(s). So, they are now already exported in
xml file for the method. Thus, no need to duplicate export in _catalog_keys file.

Also, installation should take care of the changes.

Also, add tests for them

[erp5_core]: No need to have export_properties action for ERP5 Catalog as we do cleanup of old manage_exportProperties function

According to guidelines, documents should have 'edit_workflow'.
https://www.erp5.com/documentation/developer/guideline/programming/erp5-Guideline.Programming.Naming.Conventions#never-forget-edit-workflow-on-documents

This follows the guidelines and also make it feasible to go to listbox
to search or make changes in sub-object list.

Also,
- Add 'More columns' in listbox for viewing Catalog Method list.
- Add title field in listbox view for Catalog content and Catalog Filter List
- Fixup links on these views which were not consistent.

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

When accessing an ERP5 Site, we might have automatic migration of
tools. When this happens, we might not have yet access to scripts
like ERP5Type_asSecurityGroupId.

There was already try/except, so just move slightly more code
inside.