Authored by "Hugo Ricateau"

python promises can define sense, test and anomaly method.
test method will be called by slapgrid or when no bang is needed for the promise anomaly method is
called when a promise failure required to bang the master, anomaly method can be optional but it's not the case for test method.

Slapgrid always run promises and save the result in .slapgrid/promise/result in a JSON format. The result will be used later by monitor
When a partition is correctly deployed, slapgrid will only run promise anomaly and will bang if there is an error and if the failed promise can bang

check promise anomaly when partition is upto date

Sort paths on the template_keep_last_workflow_history_only_path_list.

Reimplement the Creation of Trial Request to be compatible with renderjs/jio approach. Use Trial Condition for define what are the trials available to be requested.

On the core of SlapOS for a full autonomous deployment, it is required frontend and re6st normally. Include initial products for make easy the user to deploy it.

By "delete" is done by close Assigments or Invalidating Documents.

Obviously It was a horrible idea :)

On slapos master, the TrackingAPI is only used for determinate location/project to for computers and/or Instances via Internal Packing Lists only.

The goal of this change is not allow others movements "change" location of the item and speed up by simple reducing table size to optimal point.

To execute a slapconsole script, we could only do:

`slapos console < script.py`
but this does not stop in case of error

or
 `echo 'execfile("script.py")' | slapos console`
but this is too complicated.

Extend this API so that we can simply use

`slapos console script.py`

inspired by `python script.py`


/reviewed-on !39

When the workflow history is too big the response time
of getCreationDate is too high.

Use Cache to avoid recalculate it.

This prevents elements be moved arround.