As part of a manufacturing, we can have products partially built (thus having a particular
industrial phase). However current code prevent setting as part of transformation lines a
resource associated to a particular industrial phase. There should be no reaons to avoid this.

industiral_phase is added to amount to allow getGeneratedAmountList (which is using
temp Amount documents) to handle correctly industrial_phase

/reviewed-on nexedi/erp5!586

Reindexing a delivery is always recursive so in scenario where lines are added
by many different builders and the values in property_dict are always the same,
the useless reindexing was slower and slower. In the worst case, each builder
adding 1 line, the number of reindexing activities increased quadratically.

See also commit c020b93b.

-  [renderjs_ui] add object_jio_print to newly introduced "Export" in editable form

Displaying link as block make the text difficult to select for user

[erp5_web_renderjs_ui_test]: Use wait_for_content_loaded macro in go_to_foo_relation_field_view macro

Rely on using notification macros everytime we have some notification in
tests.

This will ensure that whenever we use save macors, it'll use the notification
macros to test for the correct notification hence minimizing code duplication.

Also, Use wait_for_content_loaded macro after we use notification macro in save to ensure that spinner is cleared after notifications

[renderjs_ui+hal_json] Add information about previous view (using form_id) to actions/workflow links

ActiveProcess is not a Folder.

It became superfluous with commit 797a8c29.

To not receive catalog already tainted by clearing & reindexing.

In turn, this allows testing catalog reference content for equality:
catalog must be exactly the same before/after an ERP5Site_reindexAll, and
before/after a hot-reindex. So issubset is not an acceptable method.
Instead, use assertItemsEqual, and raise max diff size.

Also, tidy code a bit:
- Avoid clearing catalog only to restrict result set.
- Improve coding style.
- Simplify code (single-use variables...).
- Call assert methods producing more helpful error messages on failure.

And not the implementation detail of what type of activity may spawn in
the subsequent reindexation.

WARNING product/ERP5Form/ListBox.py:987 DeprecationWarning: Each line of the
"Sortable Columns" field property must be in the form "<column_id> |
<cast_type>", where <cast_type> is one of ('', 'float').

PublicHoliday_view

These are done through 'validate_action' not at 'validate' Workflow transition.

text_content_{error,warning}_message_list was properly set through
Component_modify Interaction (used for editing Component) which checks the
source code without raising an exception.