As there is no way to have returned object, generate random value and reuse it
later to fetch exact object.

Also extended tests with Order Line checks.

sla_xml have to be passed always. As this test have to work on low level API
it is required to follow such API.

It supports cases when Person is in middle of requesting of Software
Instance.

User cannot fetch his instance until related sale order is not confirmed.

brctl is the only command which remains mandatory (except if alter_network
is false), as it is used to fetch information from system that even an
unprivileged user can see.

Example use:
PATH=$PATH:/usr/sbin ./bin/slapformat -cdv slapos.cfg

Prepares for incomming monkey-patching.

Output system commands and system-altering functions from python's os
module.

SLA XML is stored on Software Instance, but in many place the dictionary have
to be used.

It will be later used to follow SLA.

Later is shall be used in order to being followed.

It is easier to store on higher level, as pure XML. Other methods will have to
unserialise data from XML, which would be needed anyway in case of storing
them this way.

This reverts commit 79f0aaea.

More code analysis is required in order to being able support required cases
with parameters passed by user.