Check SimulationMovement_buildSlapOS no-op behaviour on delivered Simulation
Movement.

Check behaviour of Delivery_updateCausalityState in case of been called on
documents with various states.

Also deliver immediately.

Also drop 91761c1a, as in SlapOS deliveries
are not merged together.

Nevertheless 91761c1a introduced serious bug: as root_applied_rule.getPath
was not passed, searchMovementList from builder was returning a lot of
movements in case of system which has this alarm disabled, thus resulting in
enormous transaction per SimulationMovement_build*.

Even worse: passing path and explanation is mutually exclusive, as path is
internally recalculated by explanation.

Originally system would create compensation movements in case of difference on
frozen movements, but this is explicitely disabled.

The history of Hosting Subscription is fully written before alarm can chance to
run.

The HostingSubscription_requestUpdateOpenSaleOrder is required (and tested).

Trigger Open Sale Order update in case of:
  * validated Hosting Subscription without validated OSO Line
  * archived Hosting Subscription without invalidated OSO Line

Trigger change on Person level by using scripts which are locking themselves,
so only one will run per Person.

As alarm is not critical for system operations run it only once by hour.