Documentation says this step is done in one transaction, so implement
this as documented.

Detecting developer mistake and automagically running this step in smaller
transactions if more than 100 documents seems unnecessary. At least, it
contredicts documentation.

now that we use alarm sense method, another `notify` call is activated

This should fix some race conditions which made post-upgrade steps not
executed sometimes.

* each steps use an defaultActivateParameterDict so that activity they
  may create inherits the same tag, so that next step also runs after
  this). This makes it possible for example to use post-upgrade step on
  documents newly installed in upgrade step.
* use tag / after tag between upgrader steps instead of checking if
  previous alarm had errors. We also now allow force running only one
  step regardless of the previous step completion state, there was no
  strong reason to prevernt this.
* do not use two different active sense and fix method for alarms, just
  use an active sense method understanding `fixit` parameter

It allows idempotent result on any test node

replace method_name:method parameter instead of replacing form action, otherwise method_name like listbox_setPage does not work.

unescape_chr is executed with such string: "C:\Program Files\1234.jpg".
Prevent failing, and return original string in such case.

Previous behavior was to generate reference this way : `sanitized title` if reference was not already existing else `random "-" sanitized title`.
Now it generates `sanitized title "-" random` with:
- `random` at the end to maximize search engine optimization;
- `random` every time present to prevent creating document with the same reference by mistake.

+ update tests

added possibly by mistake.

see 1cb54350

We now use URL only, old address + port way is obsolete.

host and port configuration is obsoleted by URL configuration

Build a conversion_server_url from conversion_server_(hostname/port), so
that we can already stop using the old parameters

The ImportFixer AST processor wasn't correctly handling the alias
for imports. Now it takes them into consideration correctly. A test
to cover this case was added.

The old hack used to catch some exception is not required anymore.
The bug is gone with upstream updates.

So that a jump to the attachment file can be performed

/reviewed-on nexedi/erp5!158

This is a duplicate of !150, because by unknown reasons it's showing problem to merge.

Before, we we're redirecting `sys.stdout` and this doesn't play nice with the
distribute architecture of ERP5 and our Jupyter kernel needs to be adjusted for this.

So, we're now using an AST processor to fix print calls. It will modify the print
and make it write to a different file-like object. All the writes are collected
after code execution and sent to Jupyter.

It's still necesasry though to fix print inside other libraries. But for this
deeper investigation is necessary because we cannot replace print as a statement
inside `exec` contetx, it needs to be used as a function. Code can be compiled to
run with `print` as a function, but then external libraries calls will be
broken.

/reviewed-on nexedi/erp5!157

@Tyagov, please review.

Errors currently captured:

- environment.define call 1st argument is not a function and/or 2nd argument is not a string
- environment.define call argument is not a string
- environment.undefine trying to remove a function that is not in the environment

Proper tests were added.

/reviewed-on nexedi/erp5!144

  Performance tests were reconfigured on a new hardware, which is slower them
  the previous one. So this commit move the values to the new hardware based on
  the results after few days of result.

This is very helpful when a warehouse is splitted into multiple
stock points.

Also avoid returning no stock optimisations if no date could be
found in future.

If for some reasons loadClass was not working, it was failing totally
silently without any log. If there is any unexpected error in loadClass,
this ended up for example having some tests failing with :

RuntimeError: Malformed property definition <persistent broken
erp5.portal_type.Acquired Property instance '\x00\x00\x00\x00\x00\x00\x12\xb5'>
on /erp5/portal_property_sheets/SimpleItem

While only this was displayed in logs :

ERP5Type/dynamic/lazy_class.py", line 350, in loadClass
    class_definition = generatePortalTypeClass(site, portal_type)
...
AttributeError: __of__

Which was totally unrelated to the real problem.

So a silent initial error was the source of later unrelated errors, making
it very difficult to find the initial source of problem.

So make sure we have logs as soon as we are not able to load a class.