Notes:

Do nothing on 'calculate' instead of disabling *_causality_interaction_workflow as
these interaction workflows do not generate activities directly, and do work
that can't be postponed.

By contrast, 'calculate' transition of delivery_causality_workflow is modified
so that no 'updateCausalityState' activity is created by default.

This commit also update list of method_id which should not call calculate_causality

Conflicts:
	bt5/erp5_crm/bt/revision

Ensure permission removal is done after the indexation

Stop using the update action as the default action.

[erp5_base]
Allow Manager to solve the divergency
Pass the transition ID as the other workflow actions

[erp5_simulation]
Prevent duplicated keep_items

Fix request value modifications

Do not mark fields as required
The RJS field marks it as required, and user can't submit anymore.
Instead, use an external validator to only require the field when the user submit

clicked on the update button

Do not crash if the form can not be fetched.

Formbox context can be a listbox cell.

These are very outdated stuff (pre-Business Templates), they do not scale
and (except ImportExportSkins) try to write to a paths which should not
exist.

Especially in chrome (75), it's very hard to see selected text in erp5
xhtml style interface, especially in listboxs.
Chrome adds a background color to selected text, but this background is
almost same color as ERP5 background.

This uses https://developer.mozilla.org/en-US/docs/Web/CSS/::selection
to make it visually clear what is selected.

/reviewed-on nexedi/erp5!889

https://microsoft.github.io/monaco-editor/ as an ERP5 source code editor.


/reviewed-on nexedi/erp5!687

Simplifies activity spawning when dependencies are conditionally set:
  activate(
    after_tag=some_value if some_condition else None,
  )
instead of having to do a ** dance.
All columns involved in dependency checking are declared NOT NULL, so providing
"None" and expecting a dependency to happen was already not working.
This change pushes this one step further by allowing activity
auto-validation also happen on these activities.
Also, simplify getOrderValidationText: avoid iterating on keys and then
retrieving values, use a list-comprehension, simplify condition.
Add a test for after_tag, also covering activity auto-validation.

Unit Tests: login*() with a non-ERP5TypeTestCase user was adding ERP5TypeTestCase user anyway and failure was silently ignored.

checkValidity calls getContent, which uses the same mutex

Improve the query speed by using the default listbox sort.

OfficeJS's user blocking third party cookie will at least stop entering their credentials many times for nothing

Followup of nexedi/erp5@340accd1

Conflicts:
	bt5/erp5_web_renderjs_ui/PathTemplateItem/web_page_module/rjs_gadget_erp5_nojqm_css.xml

In ERP5 software release we now have `mock` egg installed, so we can use it in tests instead of doing manually like this:

```python
saved_method = Class.method
def patched_method():
  ...
try:
   Class.method = patched_method
   ...
finally:
   Class.method = saved_method
```

/reviewed-on nexedi/erp5!882

Change the caching policy to one hour.

Use the CDN to publish the page if the backend is down

Cache the manifest like the HTML page but force refreshing the manifest to prevent CDN cache inconsistency.

Defining it inside portal_components ledds to business template update issue.
Bypass it by defining the expected behaviour into the web section hook.

Allow the CDN to cache the content.

Use stale_if_error to allow the CDN to return content if backend is down

Unify Vary Header.

erp5_banking_cash depends from erp5_trade via erp5_banking_core.

Gadgets:

* Support `changed` flag from `erp5.js`: 

![unsaved changes sreenshot](/uploads/cff30eae0a5d87df26bac13d43e1da3f/image.png)

* Comply with translation protocol used in ERP5JS. This does not translate, because it would not be easy ( ERP5JS translate client side with a json database of message, but in xhtml style the translation is performed server side with localizer) and not so important now. What matters is just that we can somehow reuse gadgets.

Style:

* While we are at it, fix a minor annoyance that the button in "long" dialogs where not easy to reach, at least on chrome

![before](/uploads/e03a8311571806a55fd72f6923cf855a/Screenshot_2019-05-31_at_10.38.05.png)

![after](/uploads/5753bc44fbc0f69b6adfeb14b3367236/Screenshot_2019-05-31_at_10.38.37.png)

/reviewed-on nexedi/erp5!880