Translated properties are indexed in content translation table,
so nothing prevent us from using them in related keys. Since in
many places we show to user translated titles in relations, it
makes sense to also support searching and sorting in catalog.

This extends related keys syntax only for the newest syntax, so
related keys like `source__translated__title=X` would allow searching
for document who have a source relation to a document with title X.

Since any properties can be translated, if for example a property
`foo` would exist and be translatable, it would be possible to search
using `source__translated__foo=X`

This is only available when content_translation business template
is installed.

At the end of test result, we calculate the sum of test result line
retries and set it as a property on test result. Listbox will then
show for each test result line the number of retries. Problem is
that we did not set retry count property on test result lines which
were not retried, so they acquired this from the parent test result.

To prevent this, always set a retry count property on test result
and set it to 0 when they are not retried.

In 4bcf5c6a (CatalogTool: Introduce new dynamic related key syntax, 2017-07-25)
we introduced a new syntax to solve some ambiguities in the previous syntax, but
the test suite was still testing the old syntax only.

Update tests to test the new syntax and to also check the old legacy syntax.

Previously available at https://nexedi.erp5.net/web_page_module/3487.

So that it can be registered properly on load and later added through the ZMI.

ZODB Components: Tool Component: Only validated 'reference' must be considered when registering a Tool.

Otherwise setting an invalid reference will make the Component 'modified' but
try to use that invalid reference to register it and fail.

With chrome ( 85.0.4183.108 but I think it appears a few weeks/months ago )
when using erp5_xhtml_style when the cursor in the first column on the left
it's not visible, because the bold background hides it.

Default user agent spreadsheet is a 2px padding, but we have a rule applying a
padding 0 for all textarea. Revert this rule for textarea used as fields in
content.


---

## before:

The cursor is in *Description* field, left to "This style is ..." but cannot be seen.

![image](/uploads/f40262af196d799291643604b91ae2c4/image.png)


## after:

The cursor is same location (*Description* field, left to "This style is ...") and this time is visible.

![image](/uploads/bf1ec63532e2eca1fca7655a4581935a/image.png)

See merge request nexedi/erp5!1280

See merge request nexedi/erp5!1282

Previously this would be rendered as empty String
(unless we had a hidden field to define precision)

Commit adds also testListboxZeroValue in  erp5_web_renderjs_ui_test

See merge request nexedi/erp5!1173

See merge request nexedi/erp5!1262

Add a new document in the history while trying to show its latest state

Use this command on the module's list and worklist, to come back to the expected page when done on a module.

ZODB Components: There is no need for `description` and `source_reference` to be RecordedProperties.

* Not considered for `modified` state (dynamic_class_generation_interaction_workflow).
* `source_reference` sets only once at import from filesystem.

This implements Products import compatibility based on Component.source_reference
using existing import hooks so that Products.ERP5.Document.Person for example
is importable (actually returning erp5.component.document.Person module).

This only works with non-FS modules (IOW when the ZODB is accessible and
portal.portal_components is available).