When person will register to vifib in order to add his own computer and request
instance there will be incorrectly configured Sale Packing List.

Conflicts:
	slapos/format.py

It is using internally related to alarm last active process date, so create
such active process.

This reverts commit 7250ac74.

It might be better idea to just ignore this problem in test, instead of
relaxing too much the constraint.

Conflicts:

	master/bt5/vifib_erp5/bt/revision

This script is called with unprivilieged users and it does not need to access
objects (...in order to fetch uid), just use relative paths and blindly copy
values.

Do not try to use activities, as expanding of Sale Order depends on values
provided by this script.

Additionaly invoking it in activities was hiding security access problems.

Fix: use portal type while fetching data, instead while setting.
Protect: ff no custom_trade_condition is found, raise loudly.

Also, reduce the scope of one more try..except block.

Also, there is little chance for a valid user UID to be None (or a string).

Only next two months are covered.

Create only for two months in advance.

This reverts commit b590542d.

Conflicts:

	master/bt5/vifib_erp5/bt/revision

Applied Rules are generated later.

Expose missing test features.

Builders are called globally, so deliveries are appearing earlier.

Rules have a bit more complex applying logic.

Conflicts:

	master/bt5/vifib_erp5/bt/revision

variation property which comes from Item generates getVariationPropertyList.
VariationRange's property defines variation_property which also generates
getVariationPropertyList

As there is conflict which is not solved by category accessor generation
sorting (which is per property sheet) adding later VariationRange will result
in overwriting accessor for category with own one.

Conflicts:

	master/bt5/vifib_base/bt/revision

Conflicts:

	master/bt5/vifib_base/bt/revision