Rename `rjs_gadget_erp5_pt_listpage*` to `gadget_supportrequest_pt_listpage*`.
Rename `rjs_gadget_erp5_pt_form_view_discussable*` to `gadget_supportrequest_pt_form_view_discussable*`.

Web pages which ID starts by `rjs_gaget_erp5` will be include in `erp5_web_renderjs_ui` bt5. We want the custom page template only be included in the `erp5_officejs_support_request_ui`.

Rename the title of left chart to "Support Requests Pipe", right chart to "Last Month Activity"

And replace devellopement by app in titles

ECharts has better visual effect than Chartjs.
And also update the tests.

If strict_language is False, a document having the other language is
chosen if the specified language one is missing.

all_languages=True returns results grouped by (reference, language) so
that we can have several documents for a single reference.

strict_language=False returns results grouped by (reference,) only,
with considering the language priority, thus we have only one document
for a single reference.

catalog: portal_type=None or effective_date=None should mean the good default value in SQLCatalog_getDocumentValueList.

so that the utility script calling this can have arguments like
portal_type=None, **kw and have code like
getDocumentValue(portal_type=portal_type, **kw).

Sections must be in table order: table_0 and table_1 in first section, then
table_3, then table_4 and query_table must be in last query section.

No related key should hardcode "catalog" table name (or any other table
name, for that matter), so just let column mapper work.

Also, simplify code flow by removing unnecessary "if" statements.
Also, simplify returned query tree by removing unnecessary intermediate
ComplexQueries.

Fixed bug reported by nexedi/erp5@a5a2f1cd (comment 38674)

/reviewed-on nexedi/erp5!363

In the previous version, I pass the `editable` parameter on the homepage. This is not work anymore due to other people's changes(possibly due to 6a893b8d and/or 19028f05). After read his code, I move the `editable` to the `gadget_supportrequest_fast_view_dialog_js` page.

One part working on {base_category_id: [document_value_set]}, and the other
producing that structure out of a flat list of (base_category_id-prefixed)
category relative urls.
The former used to be included in the latter, but in some case caller
already has the documents handy instead of only urls, in which case we can
avoid a layer of document lookups.