This change to unconditionally create products, to make it more clear
that it's OK for test methods to change the products configuration because
they are reset at the beginning of each tests (they have always been removed
during tear down)

Using default {purchase,internal,sale} price

See merge request nexedi/erp5!1293

The space between listbox column header and icon used to display the sort order
was a bit too small, making it hard to see if the sort was ascending or descending
sometimes.

To have more space, set a margin-right on the before pseudo-element, like we are
already doing for buttons with text and icon.

erp5_web_renderjs_ui: Change date separator from a dash to a slash before sending query to Zope. If date separator was a dash, Zope DateTime does not use local timezone and date search does not work.

Now that this is supported, make it available also for default sales,
purchase or internal supply lines directly on resources. Until now,
this was only available on supply line view.

So far price were always assumed to be defined in the default
quantity unit of the resource, even though supply lines had a
quantity unit field, it was ignored. But it can be useful to
define prices using another quantity unit than the default quantity
unit of the resource, for example when a resource is purchased
in kg but managed in m³.

To support such scenario, we adjust the priced quantity unit
when applying price.

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