[orangecontrib] fix _updateProcess, first update inputs then call handleNewSignals and not the other way around

- complete signature to be `run`
- fix test
- orangecontrib: make inheritance to `Registered` instead of `OWEwoksWidget`
Because `OWEwoksWidget` enforce to use the defined ewokstaskclass which is not something we want for now (avoid task associated with gui, processes on threads...)

[converter oarnge table to XasObject]: fix issue with shape. Was probably not handling spectra with nelements.

- 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...)

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.

OWESRFWidget fir the expected design for the esrf task graph. Creating a OWWidgetTaskExecutor for example

[orangecontrib][test] add test for converting esrf task graph to ows and .ows to graph with the current est implementation

settings are not handled yet.

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)

Signed-off-by: payno <henri.payno@gmail.com>