1. use QueryFactory to process query in filter editor and listbox
2. add draft support for sort editor
3. add layout for hide rows functionality in listbox

Still non-UTF-8 bytes will be lost, but better than nothing for debugging purpose.

This will ease debugging from posted test results.
This code should be synchronous (no Blob asDataURL method for example) and so, btoa is used.

Sadly, btoa will fail with unicode character
Do not report HTML error in such case, until a cleaner dataURL is implemented

Creating a renderjs gadget that follows a standard interface
to get, edit and save spreadsheet document using jio. Spreadsheet
gadget is based on onlyOffice editor.
Format of spreadsheet document that can be edited in renderjs gadget
is xlsy. At present the spreadsheet document conversion from any
(xlsx, ods, etc) to xlsy is done automatically during first
synchronization with gadget by cloudooo.

URL navigation of ERP5JS has been fixed and test updated.

This will allow to catch possible errors.

Mostly, header gadget is rendered after the main gadget.
Remove many zelenium 'pause' command, by waiting for the expected element instead.

This is an adhoc URL command to support creation of new ERP5 document while keeping the global history usable.
Clicking on the 'back' icon on the newly created document will redirect to the parent document.

testERP5Security shows that owner queries must be done with ExactMatch

 ... so that we have setup's error message

This relies on selecting preferences using owner= catalog key.
This way also supports the edge case where the user has a "Owner" role defined in acl_users.

Also fix some comments

Stop using the patched renderJS version which forces to use a fix URL pattern (#a=b&c=d).
Instead, the URL logic was moved to the router gadget which becomes responsible to build and parse URL.

This will allow applications to support their own URL pattern (HTML5 pushState for example).

In case of the ERP5 JS UI, it provides now a stateful URL building (next URL depends on the current one).

This is used to support browser side "selection" (ie, stored query parameters), needed to support pagination from one document to another.
Example:
  * go to a module
  * filter with a search
  * click on the first document line and review it
  * click on the "next" icon, to directly see the second document without going back to the list

Stateful URL are also used to provides a "global" navigation history on the browser side.
  Example:
   * go to a module
   * click on the first document (A) and review it
   * use a jump button to go to a linked document (B) and review it
   * click on the "back" button to go back to A
   * click on the "back" button to go back to the module
Please note that this history works even if you open a new tab, as it is persistent in IndexedDB.
TODO: it will be required to clean IndexedDB from time to time to not fill it

The current URL patterns are:
  #/jio_key?a=b&c=d (used to display an ERP5 document)
  #!command?a=b&c=d (used to apply some operations on the URL)

This will prevent cache manifest update issue.

Update callers which could not be fixed so they disable the exception.
Reviewed-by: Jerôme Perrin <jerome@nexedi.com>