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.

we don't support negative quantity (it is better represented by an
inversion of source and destination), and this allows better support of
the smallest slice in ERP5, more especially in SupplyLine_asCellRange,
where the title of the cell is computed with the min and max being None
or not.

See nexedi/slapos.core!307 (b7d5041e)

The real issue is probably in the launcher.js file, but it is more tricky to fix

See slapos.core!313 (b02b2bff)

These are clone of Computer and Computer Partition, but used for virtual
computing devices, unrelated to physical hardware.

- Remove passing of **kw to query, since it would break Listbox
pagination
- Avoid code duplication
- Fix indentation

See merge request nexedi/erp5!1463

Otherwise, the object could be modified (_p_changed=1) and reindexed for nothing.

See merge request !1462

See merge request !1483

query SlapOs Master again and again if it created accordingly the Computer
Partitions as anyway scalability tests will start only when instance's state is
reported to SlapOs Master as ready. Thus in this case this check (and requests
to SlapOs Master) is not providing any valuable information at all.

See merge request !1482