Use the precache script to get the list of gadgets.
Ensure to also check the launcher gadget.

Report subgadget service error.

Replace it by domsugar.

This speed up gadget class generation (handlebars template parsing is
slow).

This attribute is only needed for the translateHTML method.
There is no reason for it to be kept in the final DOM HTML.

Add service worker precache script.

Add service worker precache script

renderJS now correctly handles relative URL.

There are 2 shemes for VIRTUAL_URL_PARTS:
- 2-tuple with SERVER_URL and subpath
- 3-tuple with SERVER_URL, vh path and subpath
This code only supported the 2-tuple version, add support for the 3-tuple
version.

Make ERP5Type.Base and ERP5.ERP5Site inherit from it.

Allows Base to consistently override methods which are also overridden in
CMF where CMF implementation does not propagate the call to other
superclasses (ex: __before_publishing_traverse__ as of CMFCore-2.2.10).
Also allows simplifying several inheritance fixups.
Also, use super() instead of explicit resolution to Base.

Also: testBusinessTemplate: drop dead monkey-patch.
_getCopy is called during BusinessTemplate installation, but not the one
on this class. Which prevents reordering class inheritance between
SimpleItem and copy support classes.
So this is dead code which is not even explaining what it is trying to do
(ex: what document should it really not be called on ? what effect of this
method is undesired ? why is the method attached to this class ? why is
the cleanup restoring the original method, when this class does not have
this method to begin with but it merely gets it from its superclasses
which are re-inherited from by documents hence overriding it anyway ?,
and it is getting in the way of reordering class inheritance so it goes
away.

Also: ERP5Type.patches.CMFBTreeFolder: Fold patch onto ERP5Type.Core.Folder.
All ERP5UI-visible (hence needing to call allowedContentTypes) BTReeFolder2
instances should already inherit ERP5Type.Core.Folder, removing the need
for this monkey-patch.

1. allow user to define custom value in dialog
2. fix rounding issue for total value
3. improve view

The category titles were missing

/reviewed-on nexedi/erp5!1065

In
https://www.associations.gouv.fr/IMG/pdf/reglt_2018-06_association.pdf (
from 2018 and applicable currently), it's written "870 dons en nature"
and "875 Bénévolat".

Eventhough in other documents from this official web site, it's still
the opposite:

 * https://www.associations.gouv.fr/IMG/pdf/plan_comptable_assoc.pdf
(from 2004) have in page 9:

> Répartition par nature de ressources
>
> 870 – Bénévolat
>
> 871 – Prestations en nature
>
> 875 – Dons en nature

 * https://www.associations.gouv.fr/IMG/pdf/benevolat_valorisation_comptable2011.pdf page 8:

> ➛ au crédit du compte « 870. Bénévolat », la contribution ;

Most of google searches yield "875 dons en nature" / "870 Bénévolat",
but let's follow this newer document.

/reviewed-on nexedi/erp5!1064

Add missing ones from
RÈGLEMENT N° 2018-06 du 5 décembre 2018
LIVRE III – TENUE, STRUCTURE ET FONCTIONNEMENT DES COMPTES
Titre II – Nomenclature des comptes
Art. 320-2

/reviewed-on nexedi/erp5!1060

Example configuration:

from `portal_activities/manageLoadBalancing`:

![image](/uploads/11e614bf8723e3cb81c7bac714a383b7/image.png)

in preferences:

![image](/uploads/9f8691ac140aab45904b98ce46aa11b4/image.png)

This way when users request lots of reports we always have at least one activity node to process other activities. ( document_conversion is a fictional example at this point )

/reviewed-on nexedi/erp5!1057

/reviewed-on nexedi/erp5!1048

This allow edit scripts or interactions to change the status message or
the status level using the same way as workflow scripts: script can set
the status text in request['portal_status_message'] and the status level
in request['portal_status_level'].

Note that part of this was already checked in accidentally in 97c40dcb

/reviewed-on nexedi/erp5!1052

When running test.erp5.testHalJsonStyle live tests, the same transaction
seems to be seeing two different users. This cause an incorrect cache hit
with the second user, which then retrieves values computed by & for the
first user.
Fix this by scoping the cache by user id, causing different cache entries
to be used.