Add new transitions to follow the same design of Software Instance and the scripts to each transition

remove stepTic because in this test the transaction should be called after create two Slave Instances with different customers and flag skip because this tests is not finished yet

Add transitions to start and stop a Slave Instance and the scripts used to each transition. The goal is to follow the same design of Software Instance

remove interactions because the scripts used to each interactions was deleted. This interactions are used to access Slave Partitions and it is not used anymore

clean up scripts, remove not useless scripts and remove part of code that is used to find Slave Partitions

revert code because the transition start_request and stop_requested were added to Slave Instance. With this, is not required check because both objects(Slave Instance and Software Instance) have this transitions

remove slave_id_list because it is obsolete and add slave_instance_list with empty list because this key was added in paremeter dict

slapos.xsd seems package global.

slapformat is small enough to be just one file.

check first if the transition exists because in Slave Instance context this transition doesn't exist

reorganize steps, rename tests to Slave Instance to follow one pattern in names and implemented tests to check that the customer B can not access a Slave Instance created by customer A

add step to test_ComputerPartition_SlaveInstance_ParameterList to check that the slave instance informations are add correctly in computer partition informations

In order to  be able to check  the uniqueness of IPv6 address  assigned to the
bridge,  the  network  interface  must  be up  from  an  administrative  *and*
operational point of view.

However, from  Linux 2.6.39, the bridge  reflects the state  of the underlying
device (e.g.   the bridge  asserts carrier if  at least  one of its  ports has
carrier) whereas it always asserted  carrier before. This should work fine for
"real" network interface, but will not  work properly if the bridge only binds
TAP  interfaces, which,  from  2.6.36, reports  carrier  only and  only if  an
userspace program is attached.