This is for a prototype of integrating https://github.com/rjsf-team/react-jsonschema-form/
which uses ajv which needs such as CSP, see
https://github.com/ajv-validator/ajv/blob/1b07663f3954b48892c7210196f7c6ba08000091/docs/security.md#content-security-policy
for more details

It is probably possible to serve that gadget from an "unsafe" websection
instead of making everything unsafe. If we go this way it seems some inline
styles are sometimes set as well.

Include modified version of SlapOS parameter editor and a prototype gadget using react-jsonschema-form

( this might also be causing problems, but it's what I used in the POC )

This is needed to fetch software release json schemas for the prototype

XXX the conflicts were not resolved carefuly:

 Conflicts:
	bt5/erp5_officejs/PathTemplateItem/web_page_module/jio_zipfilestorage-with-jszip_js.xml
	bt5/erp5_officejs/bt/template_keep_last_workflow_history_only_path_list
	bt5/erp5_officejs/bt/template_path_list
	bt5/erp5_web_renderjs_ui/PathTemplateItem/web_page_module/rjs_gadget_erp5_launcher_js.js
	bt5/erp5_web_renderjs_ui/PathTemplateItem/web_page_module/rjs_gadget_html5_select_js.js
	tests/__init__.py

This reverts commit b523fbfe.

BT name conflict

note: to use with ERP5JS, change CSP on the web site to something including
lab.nexedi.com:

    default-src 'self'; img-src 'self' data: blob:; media-src 'self' blob:; connect-src 'self' lab.nexedi.com data:; script-src 'self'; font-src 'self'; style-src 'self' data:; frame-src 'self' data:

When using report sections with title, this is supposed to create outline
in PDF, but this seem to became broken somewhere in the last 10 years.

This repair by using text:h instead of text:p and by setting
text:outline-level

To activate it, we have a preference to allow users display or not ERP5 tools

This report proably needs to be updated more, but at least use proper
getAggregatedAmountList so it no longer crash

It was not enabled in ERP5JS had minor issues

See merge request nexedi/erp5!1473

match date field id in listbox's column

When jumping from a product to multiple transformations, there was no status
message and also ignore_hide_rows was not passed, which made this jump non
functional when the corresponding preference was enabled.

Same as 896e5cc8 (Allow to jump from Product to its related Transformation
using it as Material as well., 2011-12-13), but for Component.

`object_report` and `object_exchange` action categories are only enabled
in erp5_xhtml_style. Use the `jio` equivalent categories so that the
generated report is also enabled in ERP5JS.

OfficeJS use another mechanism for actions registration, so duplicate
actions defined on the portal type is not necessarly a problem, as long as
all actions are not registered in the same app.

See merge request !1469

For some reports displaying transformations result to end users, it's much
better to have amount ordered in the same order as the model lines.

AmountGeneratorMixin was already sorting the lines, but the order was lost
during aggregation, because we used a dict, which on python2 does not
retain order. Switch to using an OrderedDict to keep the order.

This makes RSS reader somehow usable for support request RSS.

One important think to keep in mind is that because of a bug in how URL characters are (not) escaped in the dialog to edit character is that editing the feed URL should be edited from knowledge pad module, and not directly from front page. Also this should be edited by clicking Edit button, not by pressing enter.

See merge request nexedi/erp5!1467

See merge request nexedi/erp5!1470

See merge request nexedi/erp5!1455

To "mark as read" and open preview, the front page gadget uses the "md5" key,
which is calculated from "link", but we can have multiple entries for the same
links, like it's the case for officejs_support_request app.

Instead, use guid or id if available, this is what RSS/atom use for this purpose.

See merge request nexedi/erp5!1465

so user can login

Instead of expecting exactly actions with "preview" or "view" name, take any
action which name contains "preview" (or title is "Preview") or name is "view".

This makes it easier to include support request applications in different
applications, where the default actions might have a different name. This also
fixes the preview link for File portal type, because there was no "preview" or
"view" actions for File.

We received a few support requests from users who are able to change their
password but not to log in afterwards. These users probably copy and pasted
their user name with an extra leading or trailing space. In the reset
password dialog, these spaces are stripped, because Formulator by default
strips the input (unless "whitespace preserve" is on, but we usually don't
set it except in text areas).

Historically we have been completely avoiding the extra spaces and made the
login/user_id case sensitive, because login and user id were the same thing
and there have been issues when looking up user id in mariadb because of
mariadb collations, so we took the easy way of saying "logins are case
sensitives and spaces also mater", but with separate login / user id,
this can be revisited, because the login is only used to check the password
and find an user ID.

Stripping spaces from logins is a common thing these days (google, twitter,
facebook strip logins) which simplifies user experience and reduces support.

The risk of conflicts seems very low, if users are created with ERP5 Forms
Formulator already had stripped the login anyway. After this change in case
of two user names ('alice' and ' alice ') conflict, none of them would be
able to login.
We keep compatibility with users with trailing spaces, so if there is only
a user named ' alice ', without other users that would conflict (for
example 'alice' or ' alice'), this user remain able to login anyway. This
last part is probably not so important in reality, it is for compatibility
with testPasswordTool.TestPasswordTool.test_login_with_trailing_space