remove flag to skip the test and add assert to validate if the connection_xml from Slave Instance was edited correctly

Add security tests to validate roles used access Slave Instances objects using Software Instance user

Add role to allow a Software Instance access and edit the Slave Instance installed in the same computer partition and software release.

Add script to allow a Software Instance access and edit the Slave Instance installed in the same computer partition and software release.

Add Auditor role to allow a software instance user access a Hosting Subscription related by one Slave Instance. So, when a Slave Instance and a software instance use the same computer partition and software release, the software instance user can access the Hosting Subscription.

Add Auditor role to allow a software instance user access a Sale Packing List with one Slave Instance. So, when a Slave Instance and a software instance use the same computer partition and software release, the software instance user can access the Sale Packing List with this Slave Instance.

It is important to cover a case when Software Release get archived, but it is
still used on Computer.

add test to validate if a Slave Instance is installed in the same computer partition that a right Software Instance is installed

remove steps to create another one software release to force use the same software release but in different computers

add test to check if a slave instance is allocated correctly when each software instance is associated to different computer

Revert "add test to check if a slave instance is allocated correctly when each software instance is associated to different computer"

This reverts commit 4950c333.

add test to check if a slave instance is allocated correctly when each software instance is associated to different computer

Title is humand related name of computer, and reference is used by SlapOS
configuration.