is needed check the state of sale packing list, because when is requested stop one Slave Instance, the Software Instance is still running, then computer_partition.started() is called and will raise a exception because the Software Instance is already started.

revert all changes from slave_instance branch. This script should follow the master script to the error not be hide

filter the Sale Packing List with state equal confirmed because is not need try change object with another states

slave instance).

remove condition because stopComputerPartition should be called only when the transition is possible

Use software_instance_slap_interface_workflow instead of slave_instance_slap_interface_workflow, because those workflows were merged and slave_instance_slap_interface_workflow was removed

remove the workflow slave_instance_slap_interface_workflow because this workflow was merged with software_instance_slap_interface_workflow.

refactored workflow to be used by Slave Instance. The scripts were merged with scripts from slave_instance_slap_instance_workflow.

Now, the script SoftwareInstance_requestComputerPartition is able to allocate a Slave Instance in the right Computer Partition

In cases when hosting subscription is shared by many computer partitions,
which belongs to different computers all computers from this group need access
to this hosting subscription.

add tests to check that a Slave Instance will not be allocated when a Software Instance is destroyed

Implement destroy_requested state and transition and mark as soon as possible
this state in case when software instance is being destroyed. In
SalePackingList_requestStoredSoftwareInstanceState support destroy_requested,
which in case of ongoing destruction is no-op.

In such scenario no hosting packing lists shall be created.

When instance has packing list related with setup and cleanup and both are,
confirmed state in case of typical scenario (node says stopped and just after
destroyed) its automatically created instance hosting sale packing lists shall
be delivered.

Do not call checkConnected, in order to have only checkCyclic fired up.

Thanks to this it is possible to manipulate not finished (not delivered yet)
packing lists during destruction process.

vifib_base does not have this portal type, it exists only at vifib_open_trade.