translated_title is used in listbox search columns, so it's very confusing
for users if they can not use the usual % character for partial matches.

This changes the behaviour of translated_title to autodetect the presence of
% and use LIKE comparison operator in such case.

this field did not use a (my_ / your_) prefix

See merge request !1419

with previous implementation, categories_list=[...] could be included
and it would delete existing categories not included in it

So use getPropertyAndCategoryList instead of propertyIds,
that should return a cleaner list for input_parameter_dict here

2 letters code as reference, 3 letters codes as codifications

When viewing the worklist page, a request is made to traverse portal_workflow,
which translate global worklist actions including the document count.

The non regression test was failing with:

    [u'Draft To Validate (1)'] != ['Draft To Validate']

and in real usage, several messages were added to Localizer.

We should not show a link to jump to workflow configuration to end users, these
are not relevant to them and can only cause confusion.

Some erp5 view action use a TALES expression to be visible only in draft state.
When validation a workflow transition dialog, ERP5JS tries to go back to the previous view which is now hidden.

In such case, switch back to the default document view.

Do not return wrong content type

fixup nexedi/erp5@e21968ba

Because we were backing up to trash documents in the wrong order (in the example
from the test, portal_categories/test_category/removed_container/removed_document
first and then portal_categories/test_category/removed_container), first the
document was backed-up and some intermediate trash folders were created to
keep the hierarchy. Then when backing up the container, there was an error like:

    BadRequest: The id "removed_container" is invalid - it is already in use.

Similar error happens when upgrading erp5_configurator_standard, it was failing with:

    BadRequest: The id "officejs_sdk_workflow" is invalid - it is already in use.

The fix is to backup in reverse order, to back up first the containers and then
the document in containers.

This makes it a little bit easier to understand quantity and
quantity unit issues.

Since 405ee70e (SelectionTool/Listbox: Fix in calculating the start of last page in selection, 2018-10-17)
we have total_size in selection params. We don't want this to be propagated to
catalog search, otherwise it cause a warning that this is an unknown catalog key.

fixup! ERP5Workflow: testPerformance: Object creation is slower so increase maximum acceptable value.

0.0062 was still too much, we had test run taking 0.0064, set the threshold
to 0.0066 to be safe.

Sequence produce lots of useless output, which makes it slow to display test
result pages for tests using sequences, like testBusinesTemplate.
It must also be taking a lot of disk space on the server and is generally
not useful, when a test fail we have the log of the failing test.

Let's be consistent and use "Permissions" everywhere.

See merge request nexedi/erp5!1405

In English, "Open" means both the action of openning and the state when something
is open. Several workflows have the problem that the "Open" transition is
translated to something that does not describe the action, but the state.

We have a mechanism to override the translation for a state, by translating
`Word [{state_title} state in {workflow_id}]`, but we don't have such mechanism
for transitions, so when "Word" exist both as a transition and a state, "Word"
should be the translation of the transition and we should have translations in
context for all the workflow states.

Starting from PAS 1.10.0, assignRoleToPrincipal is private, only
manage_assignRoleToPrincipals can be used from restricted python.

We do nothing on these methods, but we comply to the interface.

When there is a invalid field, we trigger a notification if the user tries to save the form. But, if this notification is triggered, we don't trigger an alert when the user clicks in another page to leave.

But, if the field is invalid, the user does not click in "Save" and try to leave, the alarm is triggered.

Workflows are ERP5 Document now, we stay inside ERP5JS intead of go to ZMI