This avoids relying on implementation details by only relying on regular
API. This test should now be more robust in face of implementation changes.

Also, add an XXX about manage_test annoying behaviour.

Avoids the double-nonsense of looking the document up by path inside callee (!)
using the catalog (!!).
Also, follow naming conventions: variables containing documents should end
in _value, not in _object.

Vincent Pelletier:
- commit message
- remove unrelated change
- squash similar similar-intent commits even though they apply to
  different BTs

These methods must not be called synchronously:
- they can break catalog by not being careful enough about other
  reindexations which may happen in parallel. See the serialization_tag
  mechanism for more.
- indexation gets executed in the security context of the user causing the
  call, which may lead to an indexation result different from what happens
  when indexation happens with an all-accesses user.
These lines of code (some even commented-out) give a bad example. Replace
them with safe equivalents.

…r in (multi)relation field

/reviewed-on nexedi/erp5!556

Such tables are not visible in the ZMI (which is arguably a bug on its
own, although the ZMI is deprecated), but even accessing the setting
tab is broken as it runs these methods.
This change at least allows accessing stuff to start fixing.

The order in which messages are returned by getMessageList is undefined,
and manageInvoke refuses to execute messages which are blocked by their
dependencies. Notify depends on Alarm_runUpgrader, so it must be explicitly
ran second.
Also, avoid listing activities twice.

Here, we expect exactly two activities, one of each type, and just do not
rely on these being listed in any order (...in theory, as this is actually
assumed by the next iteration on getMessageList, but this is a separate
issues).

and fix pdf worker path

Create 2 new bt5:
erp5_minipaint for image editor gadget
erp5_jquery_sheet_js_editor for web table editor

OfficeJS bt5: erp5_officejs, erp5_officejs_jquery_app, erp5_officejs_ooffice, erp5_officejs_ui_test

The current and most-updated WebIllustration_view form is in erp5_dms, alongside the Web Illustration portal type declaration

Same reason as in 2115abc3.

Editor Fields were used to inject HTML, but the fields were
not pointing to Editor Field directly. They were pointing to
Base_viewWebFieldLibrary/my_text_content which is designed to
use a real editor (Gadget Field now) instead of inject HTML.

Some fields were changed to point to Editor Field in order to
inject HTML.

Base_viewTestPageFieldLibrary/my_embedded_text_content is also
changed to use a simple text area, like it should be originaly
designed for.