This is done by fixing Person's consistency while Person is added.

Create only one and use tag in order to avoid race conditions.

There are just two states, and unlocked one allows to request Software Instance.

Each person needs to be related with exactly one Open Sale Order.

It shall be related with exactly one Hosting Subscription and when it is in
planned, ordered or confirmed state this Hosting Subscription shall be present
on exactly one Open Sale Order Line.

Locked parttion are requested to be stopped, so client has to be able to say,
that partition has been stopped.

It checks all Persons and depending on thier balance and due date locks/unlocks.

Person is locked when thier balance is lower then configured one or when there
is ongoing payment older then accepted due period.

Person is unlocked when thier balance is higher then configured one and when
all ongoing payments are in acceptable time period.

It is required to visit every workflow object and click save after
manipulation of states.

Just two alarms which are checking is Software/Slave Instance shall be locked.

open_order_url is used rarely.

Use only one state -- locked.

But use transition, which are able to store open_order_url, if found.

Expose lock and unlock transition, which will selectively use correct helper
transitions with or without storing open_order_url.

Argument is required.

This reverts commit ee2553c6.

Conflicts:

	master/bt5/vifib_slap/bt/revision

This reverts commit 296fdfb7.

Conflicts:

	master/bt5/vifib_base/bt/revision
	master/bt5/vifib_slap/bt/revision

Changes were not added during slave_instance_cleanup work.

Person and Software Instance state has changed from slap_state to payment_state.

Person and Software Instance slap states have to be catalogged so reuse
existing column.

This is future compatible, as same state will be used to lock operations
of Person or Software Instance.