Delivery with solved state.

In order to minimise amount of non merged documents build each combination of path
and (closest) explanation in one shot and lock this building.

Note: As it is impossible to create AND-ed transaction level lock SimulationMovement_buildVifib
method is "unsafe" to be called in separate transactions.

Deliveried, expanded and solved subscription packing list.

This is: planned and solved payment.

User has posted invoice and planned and solved payment.

It is now available and gives better results than uid sort.

As in testVifibDefaultUseCase there was more and more Tic one after another
start to replace them with Call...Alarm with CleanTic. This will show expected
states of system in case of playing scenario.

Add magical method to generate the alarms and reuse it everywhere.

Note: stepTic still calls all possible alarms.

They are shortly in confirmed state, and in this case expand is required even
if state of invoice line matches catalogged state of simulation movement.

DeliveryLine_updateAppliedRule shall not be called in same transaction many times, as there is no transaction safe locking implemented in this method.

Instance can be destroyed when no cleanup delivery is related, but when order
line got cancelled.

This reverts commit 4b3c41d9.

This problem should be handled at recipe level.

Always Listen To Luke, He's Right. (tm)

As this is called in a loop, only try to find delivery lines for occupied
partitions.

Otherwise two queries lasting 0.3s each will be called in order to result with
None.

Delivery can be stopped by user without enough privileges.

And ExpandableItem does not have to be immediately expanded, there is alarm which
is responsible for simulation tree updates.