This follows alarm configuration, which just moves empty (stub) invoices for
next month.

This allow to work in case of Slave Instances.

If partition has related instance, send all required data and "trick" client
side that document is already synchronised.

Basically it reuses bang timestamp, which is controllable property, unlike
getModificationDate

Also update timestamp on each bang.

There are subobjects which do not provide validation state, which can endup in
acquisition of dangerous methods.

It allows to use catalog for searching.

Deliveries need to be edited before.

We still need it for backward compatibility
This reverts commit 9b0745baf3c1cc1871d0dc3083458e2c20810a34.

Conflicts:
	slapos/grid/slapgrid.py

More than 80 columns makes me kill kittens. One kitten per character.

 - only_sr filter and force the run of a single SR, and uses url_md5 (folder_id)

 - only_cp filter which computer patition, will be runned. it can be a list,
           splited by comman (slappartX,slappartY ...)

Especially in tests not all objects will be visited, which can result in cryptic
test failures.

There is no need to call fixConsistency explicitly in the test, as long as
user has assignment, so just add assignment and avoid repeating logic.

Path was removed by mistake from template_path_list

If invoice is empty, move it for next month instead of confirming it.

Also add comments for each transition.