Mixing states from unrelated workflows produces output which becomes hard
to understand. As a result, it was removed from Folder_viewWorkflowReport
and must not be expected by test.
Also, because of implementation detail, section order changed, so update
indices.

It is dangerous to rely on SKINDATA, as its structure changes. There is no
better solution here, so continue using it - just make it more prone to
raise rather than accidentally using the wrong item (3-tuple became a
4-tuple by prepending a single item, so [0] would return the wrong item).

Patched class' getCurrentSkinName expects a 4-tuple, although it ignores
the first value, so provide a placeholder.

This deprecates many methods to simplify the API.
This launcher should be considered as generic and reusable without forking it.

Stop using the old jIO API.

Start deprecating the custom renderJS version and its custom API (whoWantToXXX, pleaseXXX).

Those methods may be dropped later, to make notification system more generic

We now check if RESPONSE.redirect() exists, because TimerResponse does
not have redirect(). Currently TImerResponse is used only in
dummyGroupMethod (or any grouping method ?) but ideally it should be
used in any activity.

Fixes test failures.

Without this, every rendered cells would contain the concatenation of all cells
with same uid (i.e. None) in the previous page, and the size of each cell would
increase exponentially at each update.

- do not copy the result of Base_getWorkflowHistory, and only iterate on keys
- call getPhysicalPath only once
- get workflow tool only once, and without relying on acquisition

Along with related alarm, property sheet and skins.

Add support for honoring user selection, and related option (enabled by default).
Query catalog only once.
Do not use custom ZSQLMethod.

same as f310c561

+ store all ERP5 configuration parameters in the local setting DB.

Do not handle solving issues in Workflow_statusModify, use directly script attached to the
dialog of solving divergence. Also, previous code was no longer working properly with latest
simulation

Depending on the dialog's parameters, the script might get the parameter
in kw or in the request. To prevent this random use, we define it in
the parameter list

This avoid annoying messages that someone else modified the document, if the
user knows we is going to have a divergence, he should be able to use the dialog
immediately.