- An environment object was implemented to help us deal with the multiprocess
architecture of ERP5 and objects that cannot be easily stored in the ZODB.
It stores definition of functions, classes and variables as string. The implementation
uses a dumb Environment class to allow users to make `define` and `undefine` calls,
which are captured and processed by an AST transformer before code execution.

- Along with the environment object, an automatic "import fixer" was created. It does
not allow users to import modules as they normally would, because this may cause
collateral effects on other users' code. A good example is the plot settings in the
matplotlib module. It will fix normal imports, make them use the environment object
mentione earlier automatically and warn the user about it.

A few bugs were fixed with this implementation, for example:

- https://nexedi.erp5.net/bug_module/20160318-7098DD, which reports an inconsistency
on portal catalog queries between Jupyter and Python (Script) objects. Probably an
issue with user context storage in ActiveProcess

- https://nexedi.erp5.net/bug_module/20160330-13AA193, which reports an error related
to acquisition when trying to plot images, which happened in other situations, although
this is not officially reported in Nexedi's ERP5. This probably also was happening because
of old user context storage.

- normalize path to avoid to traverse with wrong value
- review KeyError message when domain is unknown
- use getWebSiteValue when possible

/reviewed-on !124

Dependency should be defined directly on bt5 if needed.

'keep_existing' argument of Base._edit has never been used
and we should consider removing it.

When defining a guard on an object, calling
a method such as Base_viewDict on that object
could be denied due to guard acquisition.

- the check is moved to a less performance-critical place
- getPortalObject was forgotten in commit d8e9ed19

- 'apply' causes a break in cProfile results
- 'apply' is deprecated (removed in Python 3)

* reference
* translated_title
* the usual owner_title, creation_date and modification_date
* remove useless listbox_editable_fields that are defined in the field library

This business template does not seem to follow the guideline yet

For example, Python Scripts were:
- dirty in the imported BT (causing all of them to be reinstalled on upgrade)
- compiled to return None

When a currency exchange line is (in)validated, we need to reindex the currency exchange
cells that acquire validation state from the currency exchange line.

This allows defining an exchange rate without end date

https://codemirror.net/demo/activeline.html

since be31425e