This reapplies parts of 9a84ef83 , but a
different server side approach:
 * use portal_workflow API to count worklists
 * introspect workflow to build queries
 * use translated state in the query, trying to be a bit more user
   friendly. We could do for portal_type as well.

This workarounds #20180907-24A654C a problem with queries generated by
gadget worklist does not seem to support complex queries with multiple
values ( local_roles: ['Assignor', 'Assignee'] ). This code generates
queries:

```
( ( local_roles:  "Assignee" OR local_roles:  "Assignor" ) AND portal_type:  "Support Request" AND translated_simulation_state_title:  "Opened" )
```

where the previous version generated queries like:

```
( portal_type:  "Support Request" AND simulation_state:  "validated" AND local_roles: (  "Assignee" OR  "Assignor" ) )
```

which did not match anything. Maybe because local_roles is handled
differently in catalog

This reverts commit 9a84ef83.

Eventhough there's a delay due to cache, the default worklist
implementation is efficient and worklist is translated.

To make it easier to test worklists and dashboard.

SR-15 Crashed! is Opened
SR-16 Boom!  is Suspended
SR-17 Done is Closed

So that ERP5TypeTestCase user is Assignee/Assignor and we can test worklists

Because worklists tests expect to run with ERP5TypeTestCase user, and this test uses another user.

 * Preferences use same icons as other OfficeJS apps
 * Support Request use an "help"/"support" icon

This is not used in this interface

now that we have ERP5 Login, reference is just reference.

Searchable and sortable

This must be from manual edit of business templates files.

now that we have ERP5 Login, reference is just reference.

It was displaying "False" when no requester, display nothing instead.

add reference which was misisng in searchable / sortable
sort in same order as columns + more columns

/reviewed-on nexedi/erp5!754

/reviewed-on nexedi/erp5!750

In web_site_module/predecessor_test_web_site/section_with_content_page.

This publication_section was already sel on the web section (but seemed not active ??), but not on the web page. Then this commit just adds the missing category and update the web page

Those classes were used by JQuery Mobile.

The tests are exactly the same as for text editor (except there is no
"migration test" which was not really to test TextEditor)

Codemirror app is now using the same mechanism as text_editor. For now, it has
exactly the same features as text editor but it will create "Web Script"
instead of "Web Page" documents. The codemirror mode is forced to "javascript"
and the content type of the document if forced to "application/javascript".

DiffTool: removePropertyList function should be working same for both ERP5 object and dictionaries of ERP5 object properties

Before we use to neglect removing some properties from ERP5 object properties' dict, which led to error in case of use
of DiffTool for Historical Revisions dict. Thus, its important for removeProperties function to act similar in both
cases.

Also, add `base_data` in attribute_set to be removed because `data`, `base_data` and `text_content` are same

This is essential to have better aesthetic of Deepdiff diff for tuples.
In general, we treat iterables as long string so as to bypass the complicated
diff for iterables provided by DeepDiff, but for tuples this was creating a
problem as it was not possible to understand the diff properly.

Hence, by soting them, we get more understandable diff for tuples.

Also, there is no need to override `__diff_tuple` function as it is itself
dependent on `__diff_iterable` which we already override.

Following convention, it makes more sense to use view mode for DiffTool view.
Also, we don't need selection as of now.

Also, update the tests

View wise, the date and path for new version/obvject should be on right side which
in our case is `your_second_date`. Thus, the case where we run diff action on single
object, the right side should show the current version and the left side shoule show
the last version.

/reviewed-on nexedi/erp5!741

/reviewed-on nexedi/erp5!748

/reviewed-on nexedi/erp5!739

/reviewed-on nexedi/erp5!740

zope.conf default encoding is also used for responses and converters, so
for consistency we should also force default encoding there.
This is especially useful when running tests, because zope.conf is not
used and default values are used.

https://tools.ietf.org/html/rfc4329#section-7 states that text/javascript is obsolete.

Doesn't really matter in the end because WebPage_viewAsWeb forces the content type.