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.

Drop user access for now.

erp5_open_trade provides open_sale_order_module.

There is no need to speed up Open Sale Order update.

Correct module name.

Switch to fully alarm based approach and drop Person.fixConsistency interaction,
which created Open Sale Order.

As Open Sale Order is optional and it is asserted by alarm drop
open_sale_order_related_constraint.

Rename script to follow naming conventions.

Rename slapos_subscription to slapos_accounting in order to follow modularity
if SlapOS Master.

Convention: test<BT Name>[description]

For getFullComputerInformation extend test with Slave Instance, and modify
original. Those test shall check complex computer, and having Slave Instance
follows the idea of computer complexity.

In case of other methods add _withSlave variants. Those tests are checking
specific access, and shall be separated from its non-Slave variants.

After requesting destruction and running simulateSlapgridUR the partitions are
free.

The user which request instance on public computer was able to read its
connection parameters and they were correctly set during simulateSlapgridCP run.

Interaction workflow are required to automate recalculation.