Open Order modification is a bit more optimised.

Prove that Subscription Item periodicity is correctly defined.

Start at least *today* and if date is in day number higher then minimum amount
of days in month *rewind* and do not fast forward.

Store processed date.

Periodicity is known when service is available.

Add dates safely using DateUtils.
Round up start_date to next midnight.
In case if after rounding this date would go higher then minimum number of day
in month set it to next month beginning date.

This reverts commit 77143759.

Building is fully done in alarms, so allow them to build.

This reverts commit fc9dfc05.

Provide three parts:

 * desire to do (Person_storeOpenOrderJournal)
 * difference to apply (Person_getOpenOrderDifference)
 * apply (Person_updateOpenOrder)

It is possible to debug current state by using src__=1 parameter passed to
Person_storeOpenOrderJournal

Raise in case of bad state.

Conflicts:
	master/bt5/vifib_slap/bt/revision
	master/bt5/vifib_web/bt/revision

Also drop not needed methods.

It is better to have few failing tests on check consistency and false positive
alarms then accidentally confirmed Sale Orders.

Support correctly stop date.
Postpone new open order creation on start date update, until update is needed.

Start and stop dates are known from open order on first expand level.