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 reverts commit 66f30ebb.

Revert "ZODB Components: Non-core bt5 with 'Document Component' overriding standard ERP5 Document must create its own version_priority."

This reverts commit ee686cac.

Revert "ZODB Components: When migrating FS Mixin, set the ZODB Component reference to the class name (like Interfaces)."

This reverts commit 2b8c6305.

This reverts commit 937500a1.

Revert "ZODB Components: Resetting Portal Type classes was also clearing Interfaces of erp5.component.* modules."

This reverts commit f1f415a3.

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

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.

- use global preference to get publication section value
- test updated

/reviewed-on nexedi/erp5!1017

ZODB Components: Resetting Portal Type classes was also clearing Interfaces of erp5.component.* modules.

__implemented__ and __provides__ attributes are cleared on Portal Type reset
to break a circular reference (11e2b506). Resetting of ZODB Components is
done independently of Portal Type classes, so until the next ZODB Component
reset, Interfaces were not implemented anymore.

11e2b506 states that this creates a memory leak but this is not actually true
as Python garbage collector will break such circular reference and collect
this object, as asserted by a newly introduced Unit Test. This is probably
less efficient than explicitly breaking the circular reference and thus relies
on reference counting (rather than the garbage collector) but doing otherwise
would require introspecting ZODB Components module to find classes implementing
Interfaces (erp5.portal_type only contains classes).

This only takes care of ZODB Components modules but maybe breaking circular
references for Portal Type classes is not even needed (if so, this will be done
in a later commit).