Quantity unit was not defined in default supply property sheet, so the
fields were created local properties, because the accessors were not
existant. This change make the accessors for quantity unit on default
supply lines generated.

The implementation details is that it replaces priced_quantity, which was
defined twice

See merge request nexedi/erp5!1494

Update local frontend slave with backend balanver's IPv6 address if Test Suite is configured to use a local frontend slave. This allows a develop to use a local frontend (possible in same machine) and avoid network effect from generated test results.

See nexedi/erp5@1b5e3c72

See nexedi/erp5@1a807abb which removes one translated string

Stabilize random failures

Add some assertElementPresent right after the waitForElementPresent to stop the stop in case of missing element.

This page gathers all informations linked to the current user: preference, person, language, logout.

Drop all other language/preference links from other gadgets.

Drop user informations from language page

Firefox disables IndexedDB in private mode.
Use memory storage in such case. This allows user to have a normal erp5js usage until the window is reloaded.

See merge request nexedi/erp5!1493

1.use query factory instead of manually query
2.don't get all related object, use modification date to filter
3.synchronize only related service

See merge request nexedi/erp5!1490

To be compatible with xhtml, where in hash scripts like Base_getMultiListFieldPropertyDictList
the category titles are not translated and translation happens in form rendering

Also:
erp5_web_renderjs_ui_test: Add testParallelFieldListTranslation

to check the translation of category titles in parallel list field

When some types of files are attached to a forum thread, they may be
subjected to a portal type migration. This is the case of CSV files, for exemple. What
happens in that case, is that the document D1 is created with portal_type PT1, then
discoverMetadata is called, which triggers a portal type migration. Then D1 is deleted, and
recreated as D2 with portal type D2. The problem is that the migration happens after D1 was attached to
the Discussion Post (in a different transaction), so the relation between both is broken.

This can happen if there is an error very early during publication.