- rename `process` to `run` and
- replace output.var_namevar.value by outputs.var_name and input.var_namevar.value by inputs.var_name
- _INPUT_NAMES and _OUTPUT_NAMES where missing (larch processes...)

update value from list to set

For now process is always call. When call from workflow_concept it insure the input has benn provided previously. Otherwise you should provide the xas_object. It might evolve with time.

Add some simple unit test to insure an orangecontrib est workflow can be converted to a graph and a graph to an est workflow.
Add test to insure we can execute it as well

Make `Process` inherit from Task
Create a OWESRFWidget which inherit from OWWidget and implement stuff for the task graph.

processing source code used:

input_ows_file = "..."
from esrf2orange3.owsconvert import ows_to_esrf, esrf_to_ows
from esrftaskgraph.graph import TaskGraph
graph = ows_to_esrf(input_ows_file)

* _NexusDatasetDef: can now have some units defined by latex: `units_latex`
* _NexusSpectrumDef: can now have a `title` and a `title_latex` defined

In fact instead of having to repeat those definitions n times we should have some king of a database defining those once for all

- add `outputs` and `inputs` entries in processing classes used in ppfaddon aliases file.
- add `get_xas_obj` function in est.app.utils module
- mode est.app.utils._convert_spectra_dims to public

[orangecontrib] add _ParameterWindowContainer to add a auto/manual option for computation in OW from larch and pymca

[core]register_process: add a relative_to parameter to store numpy array relative to "r" values and not only "energy"

[core][larch] fix creation of the new secptrum object when overwrite is True in larch process wrappers