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

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

add local_permission_vifib_interaction_workflow to Slave Instance and assign the interactions follow the same design of Software Instance in this case

Use default user to check the objects because the user as customer can not access all objects to check if are different. Add new test to be implement later

add steps to test_request_SlaveInstance_twice. This test is to check that requesting a Slave Instance twice, the instances are created correctly

add new step to test_Person_request_SlaveInstance_Two_Different_SoftwareInstance. add new step to test_Person_request_SlaveInstance_Two_Different_SoftwareInstance. This step is to check if the slave instance and software instance with the same software release are allocated to the same computer partition

Old version of slap library are not using state parameter, so prove that new
version of Slap Tool is capable to speak with them.

implement test_Person_request_SlaveInstance_Two_Different_SoftwareInstance. This test is to check that one Slave Instance is allocated correctly when exists two different Software Instances and Computer Partition. The slave instance must be allocated in Computer Partition that exists one Software Instance with the same Software Release.

Do not try to request start not fully installed computer partition, and wait
until instance setup packing list is stopped, before trying to create hosting
one.

Beside of setting state on Software instance by start/stop requested methods
setup in activities real request. Thanks to this *after* computer partition is
installed (instance setup packing list == stopped) the request becomes
synchronous (...a bit later -- in sense -- just once called).

It shall check for instance hosting, not instance setup.

Setup all required parameters before requesting again.

If internal bootstrap is used there is no need to clutter arguments with not
required command.