Also minimise activity hurricane by calling expand directly.

Open Orders are searched using indexation timestamp, which allows to see them
in "windows", and does not repeat expand if not needed.

Generate activities and allow to pass the tag. Use search and activate
everywhere which will allow to walk through objects without killing the cluster
even in case of really big documents.

Avoid calling isDivergent which can take few minutes to finish.

causality_state comes from well designed causality workflow, which informs
enough about delivery state. Fetching causality_state property is extremely
fast.

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

This merge request is trying to provide an API so that we can construct urls in a more organised manner than manipulating strings.

The motivation, started from this merge request: nexedi/erp5!333, where absolute_url is overriden for Web Section and Web Site. Then we found that we have to do many dirty changes like:
```
              absolute_url python: here.absolute_url();
              absolute_url python: absolute_url[:-1] if absolute_url.endswith('/') else absolute_url;
```
(more of those in nexedi/erp5@f601d7a5).

So we said we should make an API to have an organised manner, like we have e.g. Base_redirect to handle redirects.

- First commit adds this as a script in erp5_core, along with a test.
- Second commit uses it. It is not on my scope to change all erp5 code, but I focused on changing on the things I already had to in
nexedi/erp5@f601d7a5

@romain , @kazuhiko please make comments. Tests passed, but not on the final revision (did some amendments) and I think better not to re-run suite  before getting comments. Also, @tatuya , I think you are responsible for ERP5 interfaces, so I would like your opinion if erp5_core is the good place, or maybe some other BT or product.

My plan would be to merge this and then nexedi/erp5!333 rebased on this. But in any-way this should be separate from nexedi/erp5!333.

/reviewed-on nexedi/erp5!431

Use Jio 3.26.0 in erp5_web_renderjs_ui and  erp5_core

/reviewed-on nexedi/erp5!491

/reviewed-on nexedi/erp5!490

fix attachment parallel synchronization issue

inotifyx is has no support for Python 3 and
it does not seem to be maintained anymore.

/reviewed-on nexedi/erp5!484

The erp5 site creation fails due to a dependency error. Dependency to erp5_full_text_myisam_catalog was added to the erp5_scalability_test business template.

/reviewed-on nexedi/erp5!483

fast synchro is not ready.

Note:
This is not a complete work, i.e. it is not supposed to update all url
calculations of generic ERP5. It is done so that:
- Other pending work can use it
- Demonstrate how the API should be used and test it

for a base document, given the form_id, document_reference and GET parameters

Commit contains also a test in testERP5Type

Allow to overwrite this inside project to init Properties like reference.

Because it is mainly used from the 'initsite' zope.conf section, the passed
value is often a string, hence the automatic cast to integer.

The default is defined in erp5_core: 1
The specific value '0' disables storage in ZODB.
Another other value sets the interval.

- Use unrestricted _edit method on reportTaskStatus - restrictedTraverse applies security anyway
- Remove some useless code
- Fix TypeError: stopUnitTest() takes exactly 3 arguments (4 given)