fix steps because this test must validate if the Slave Instance is stopped correctly according to one production scenario

Force the update of Computer Partition is any Slave Instance is allocated
or stopped. This make the system automatically update configuration if
the new slave instances be created.

add steps to install another software release in the current computer partition to force allocate the Slave Instance in different computer partition

When some Slave Instance allocated on some computer partition, it
trigger the "start" broadcast and sometimes some Sale Packing Lists are
already started, long ago.

Refactor steps to validate if the exception NotFoundError is raised correctly when a software release is not installed in the selected computer partition

Add step to select a random computer partition. This method is used to select one computer partition that does not exists one software release and one software instance installed in this partition. For now, the first one is enough

Revert "add step to be possible select a random computer partition. For now, select the first one is enough. This step will be used to raise the exception NotFoundError"

This reverts commit 07b4cd7f.

This reverts commit 93c0ee87.

add step to be possible select a random computer partition. For now, select the first one is enough. This step will be used to raise the exception NotFoundError

add test to check that a Sale Packing List with the state stopped and associated to Slave Instance is ignored in getInstanceParameterDict()

Instance

Such transitions are required.

This change is required to not return more movements that is expected.