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

This reverts commit f1f415a3.

This reverts commit 2d6d1556.

This reverts commit d220132e.

This reverts commit b5276b14.

This prevent getting DB read/write conflicts

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 make everything slow as hell and prevent to quickly save.

Having WebPage_viewAsWeb in default skin selection break other sites
relying on default behavior of erp5_web.

See merge request !1071

Also, move test_data folder to Products.ERP5.tests as this does not need to be in the ZODB.

And we should keep erp5_core as small as possible.

Display like this:

![image](/uploads/0e182e76a94c56eb450e8ef354a9c5c1/image.png)

Where we can easily read in listbox the history of item movements: 
```
   → A
A  → B
B  → C
```

instead of

![image](/uploads/24bea37097dc22c2eaedf323d049aeb3/image.png)


```
A 🠐 
B 🠐 A
C 🠐 B
```

( as always, this also enable coding style test )

/reviewed-on nexedi/erp5!1061

This was failing [coding style test](https://nexedijs.erp5.net/#/test_result_module/20200305-AB828AA2/54)

/reviewed-on nexedi/erp5!1070

Keep compatibility with existing officejs tests, by keeping the
data-i18n attributes, even if useless.

Chrome will deprecate appcache in the coming weeks.
As appcache has been dropped on Firefox, this change will improve the speed on Firefox.

The service worker only provide a cache for all ERP5JS gadgets.
ERP5JS will still be usable on browser without service worker API.

The list of files to cache is directly added inside the service worker
code, in order to be able to skip the usage of the fetch method (which
does not yet cover all browser HTTP usage).

This list is configurable on the web site level.
No need to change the service worker code directly.

The service worker will be updated as soon as the web site modification date changes.

End user does not need to reload its browser tab.
Only browsing ERP5JS will trigger the service worker update.

When a new update is found, ERP5JS will automatically reload itself if
there is no risk of losing user data input.

An empty appcache is kept, to allow migration of existing client to the
worker automatically.