erp5_officejs: Updated Appcache and jioConf

This is an hardcoded behaviour of the app to allow user to manually enter the websocket url

This allows to store any arbitrary value as jio configuration.

also commit the new values on the fields "date" in proxy field libraries as
they are not automatically recomputed for now when changing config on a proxy
field

This allow to configure local properties (like language) in the browser database through jIO.

- Translate portal_type column, and move it to more columns
- remove creation_date & modification_date editable fields, they are already in the proxy field

fixup f4639fde . params['section_uid'] can be a integer

fixup 5ae7e594

and fix a typo

This column shows an icon to download the document for each document in the listbox

They are used by RSVP.js when calling the Promise.cancel method

This top gadget can be reused by any HTML5 application who want the same layout.
The configuration is done on the Web Site level with the 'WebSection_viewHateoasPreference' configuration form.

define security on the right class
use newstyle class so that slots is effective
cleanup whitespace and indentation

This reverts commit ca125dac which came
from a misunderstanding. The code does not modify or convert any date, it just
display a default timezone when creating a new object.

Also fix the date field to have a timezone property in former proxy field library

This reverts commit fd28ecaf which is no longer needed as the try/except of the NotConverted exception has been fixed at a lower level

Redefining class prevent the try/except from working as
it is not the same class which is raised.
Fix import order to prevent looping

Take into account remarks done by Julien and Vincent.
Also stop using deletePycFiles for git repositories, git clean -fdx
is doing better (it remove more useless files if needed)

this generated errors when looking at alarm results

Using an instance of the class from the script create a huge memory leak
in zope which does not happen when instanciating class from the code.
The issue seems to come from the use by the matribox as simple test cases
of instanciation from script do not reproduce the memory leak

It is automatically created and provided by the ondatachannel event listener.
This bypasses some Chrome bugs.