We need to link interactions to scripts scripts that needs to be executed :
- after interaction
- before interaction
- at the end of transaction
- later

* The type Workflow was used by configurators, no other usage was done
* We would like now to use type Workflow for replacement of DC Workflows, and since configurators have specific code, there is high chance to break compatilibity
* To keep configurators working, move all previous usage of Workflow to ConfiguratorWorkflow
* We would later need to migrate previous Workflow objects to ConfiguratorWorkflow (all the ones used by configurators)
* Configurator Workflows does not make any usage of Variables, remove forms and types

DCWorkflow to ERP5Workflow: copy or move some Workflow form to be used only on Configurator Workflow

Design of Configurator Workflow is kept as it is. But Workflows were changed a lot. So some
parts of configuration of Workflow is copied for Configurator Workflow

Work partially done by:
- Wenjie Zheng
- Isabelle Vallet

We already had several portal types for workflows in erp5_worklow. Since we will soon use
ERP5 style workflow by default, portal types must be part of core business template.

We already had several forms for workflows in erp5_worklow. Since we will soon use
ERP5 style workflow by default, forms must be part of core business template. Changes
to forms will be commited later.

Transition of Interaction Workflows are now ERP5 objects, thus needs to have propertysheet

Work partially done by:
- Wenjie Zheng
- Isabelle Vallet

Guard was only handled as an expression. To fully support all features of
guard, a complete propertysheet is required with group, permission, role,
expression.

Work partially done by:
- Wenjie Zheng
- Isabelle Vallet

Move specific Transition properties of Configurator to a dedicated propertysheet.
Configurator could be reviewed further later to share more code with new Workflows.

Work partially done by:
- Wenjie Zheng
- Isabelle Vallet

Worklist are now ERP5 objects, thus needs to have propertysheet

Work partially done by:
- Wenjie Zheng
- Isabelle Vallet

ZBigArrays were omitted from being saved in notebooks in 5fb16acd
(erp5_data_notebook: Don't save ZBigArray in data notebook. It may be
too big that zope process may crash.).

However since ZBigArrays are regular ZODB objects with persistent
references to other ZODB objects there is no reason for us not to be able to
serialize them.

Add corresponding FIXME with link to more context.

/reviewed-by TrustMe

Currently the full-upgrade alarm calls the 3 upgrade-related-alarm's activeSense methods in activities. As activeSense method runs Alarm's methods in activities too, the final activities do not get the good "tag" and "after_tag" values, which creates a lack of depency between them. In consequence, if we are not running the real upgrade (= just activeSense), no need to run post-upgrade's activeSense : indeed, post-upgrade constraints will be run on what are *currently* installed, and not on the result of the previous steps of the upgrader, which lead to a wrong and misleading consistency check.

This Merge Request intends to fix it by : 
   * Adding a "activate_kw" parameter to activeSense method, which allow to configure its internal call to "activate"
   * Improving upgrader to remove the useless calls to activeSense, and properly parameterize activeSense's activity generation 

/reviewed-on nexedi/erp5!276

For new developments, we should use portal_components. So move theses tests to
portal_components before Workflow changes.

There is no selenium tests yet, but at least we can see the same graph rendered with different
gadgets. Later, we will have to find smart ways for testing graphs

[erp5_officejs_appstore_base] configuration_latest_version is set when acception the Software Publication

Fix web section templates.
Fix appcache for the redirect app.

FullUpgrade Alarm relies on getLastActiveProcess to return results, which makes
use of the catalog to return a result. If the Active Processes spawned by the
3 Alarms composing the upgrader (pre, upgrade, post) are not indexed before
the FullUpgrade Alarm collects the results, then the wrong active result is
returned, which then give the wrong feedback to the user.

It seems that the "defaultActivateParameterDict" method cannot overwrite
the "tag" parameter of indexation activities (even if it was working for
after_tag). This is why this commit is needed.

to fit original script behavior, from erp5_web skin folder.
Also fixes "KeyError: TraversalRequestNameStack" from
`WebPage.getDocumentValue(reference)` on the "View" skin selection.

This activate_kw is a dict passed to internal 'activate' called
in order to more controls on activities created by activeSense

As results may be inconsistent as long as pre-upgrade and upgrade steps have been run for real