Using the legacy API was broken and this is also to prepare
DocumentationHelper and ClassTool removal.

Some Constraint Property Sheets and Views in core bt5s were defining
properties whose Portal Types (and sometimes their Views as well) were
available in a non-core bt5s.

BusinessTemplate: Get rid of spurious warning when skipping update of Local Roles for non-ERP5 objects.

- Do not enable on all password fields
- Allow specifying strength metter for a given field
- Allow customising password validation rules by changing properties
(allows different rules in the same page)
- Login similarity check can be done by adding login as a sequence
or blacklisted word, as desired
- No hard rules of what a strong password is, instead use a reward
system for using varied characters & character classes, reduced
when password contains widely known sequences or too common
passwords.

erp5_autocompletion_ui: Add JS ERP5Autocomplete() parameter to transform text before sending AJAX request.

For example, if one wants to uppercase/lowercase the value entered by
end-user.

erp5_autocompletion_ui: Autocompletion property value set to the field should be the one queried from the Catalog.

erp5_autocompletion_ui: Consider that description may not be needed, thus only one line, the label, is displayed.

Possible through defining a TypeBasedMethod (PORTAL_TYPE_getCompletionDict)
returning a dict serialized in JSON by the calling method, or otherwise
overriding fallback script (Base_getCompletionDict).

erp5_autocompletion_list: Move away generic JS code from RelationField as it should be reusable anywhere.

Limit the number of results to 15 instead of 20 as it seems to be enough (taken from an existing customer project).

RelationField: Implement autocompletion and use it by default once erp5_autocompletion_ui is installed.

This reverts commit 264459a7.

Sorting by title on the module listboxes does not make sense because of the
way of the default title generation.  (ex SO-1,..SO-100 are sorted SO-1, SO-10)

Also, specify missing CountMethod in the listboxes.

erp5_autocompletion_ui: Increase delay before searching from 300ms (default) to 600ms, this should be enough...

For example, MultiRelationStringField does not return a plain value, but a
MultiRelationEditor overriding Base_edit default behavior.

So, Relation Fields in ListBox were ignored during validation as the input
value is compared with the current (default), thus the field could not be
cleared as the value from the actual object was not retrieved at all.