Do not access form submission REQUEST from the listbox list method,
as it is rendered asynchronously in ERP5JS

This reverts commit 35b2c024.

Allow edition in the new UI

This make everything slow as hell and prevent to quickly save.

Example: <h2 class="foo">bar</h2> => <h3 class="foo">bar</h3>

Changing the language and browsing to another web section require to fully refresh the page.

This breaks the previous gadget API.

Base_getDialogSectionCategoryItemList was supporting the case of
users from zodb_users plugin, but not the case of ERP5 users with
roles set from zodb_roles.

It's a more and more common case to make manager users using a
"normal" ERP5 user as person (so that we can reset password etc)
and to give Manager role by zodb_roles, but this was not supported
by this script.

Now that we properly detect 0 tests as errors/UNKNOWN, this test was reported
as UNKNOWN state. Run the tests, but as expectedFailure since they have not
been updated since b4b5bcf8.

See merge request nexedi/erp5!1259

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.