Revert "Fix the name of the virtual machines for the psdk-test"

This reverts commit b7e68a3f because the
automation script still needs to be adapted to run under the
restrictions faced by RBEI. The test case will be updated once the
automation is updated.

Signed-off-by: Peter Senna Tschudin <peter.senna@collabora.com>

test-cases/sdk-persistent-disk-etc.yaml

@@ -48,7 +48,7 @@ run:
     - The stage1 command will setup the test environment (create and clone VMs)
       and also will execute any necessary step for the initialization of the test.
       After execution of stage1, there should be a virtual machine running
-      named apertis-psdk-test-old-sdk, proceed to the next step.
+      named Apertis_OldSDK, proceed to the next step.
     - "Use psdk to initialize the empty disk and to configure the SDK to use it:"
     - ~https://developer.apertis.org/latest/sdk-usage.html#preparing-the-persistent-disk-on-the-old-sdk
     - "The SDK will reboot when the configuration is completed. After the reboot
@@ -56,7 +56,7 @@ run:
     - "Continue executing the second stage of the test:"
     - $ psdk-test> r
     - "After the execution of stage2, there should be a virtual machine running
-       named apertis-psdk-test-new-sdk, proceed to the next step."
+       named Apertis_NewSDK, proceed to the next step."
     - "Use psdk to configure the SDK to use the persistent disk:"
     - ~https://developer.apertis.org/latest/sdk-usage.html#using-the-persistent-disk-on-the-new-sdk
     - The SDK will reboot when the configuration is completed. After the reboot

test-cases/sdk-persistent-disk-home-user.yaml

@@ -49,7 +49,7 @@ run:
     - The stage1 command will setup the test environment (create and clone VMs)
       and also will execute any necessary step for the initialization of the test.
       After execution of stage1, there should be a virtual machine running
-      named apertis-psdk-test-old-sdk, proceed to the next step.
+      named Apertis_OldSDK, proceed to the next step.
     - "Use psdk to initialize the empty disk and to configure the SDK to use it:"
     - ~https://developer.apertis.org/latest/sdk-usage.html#preparing-the-persistent-disk-on-the-old-sdk
     - "The SDK will reboot when the configuration is completed. After the reboot
@@ -57,7 +57,7 @@ run:
     - "Continue executing the second stage of the test:"
     - $ psdk-test> r
     - "After the execution of stage2, there should be a virtual machine running
-       named apertis-psdk-test-new-sdk, proceed to the next step."
+       named Apertis_NewSDK, proceed to the next step."
     - "Use psdk to configure the SDK to use the persistent disk:"
     - ~https://developer.apertis.org/latest/sdk-usage.html#using-the-persistent-disk-on-the-new-sdk
     - The SDK will reboot when the configuration is completed. After the reboot

test-cases/sdk-persistent-disk-sysroot.yaml

@@ -51,7 +51,7 @@ run:
     - The stage1 command will setup the test environment (create and clone VMs)
       and also will execute any necessary step for the initialization of the test.
       After execution of stage1, there should be a virtual machine running
-      named apertis-psdk-test-old-sdk, proceed to the next step.
+      named Apertis_OldSDK, proceed to the next step.
     - "Use psdk to initialize the empty disk and to configure the SDK to use it:"
     - ~https://developer.apertis.org/latest/sdk-usage.html#preparing-the-persistent-disk-on-the-old-sdk
     - "The SDK will reboot when the configuration is completed. After the reboot
@@ -59,7 +59,7 @@ run:
     - "Continue executing the second stage of the test:"
     - $ psdk-test> r
     - "After the execution of stage2, there should be a virtual machine running
-       named apertis-psdk-test-new-sdk, proceed to the next step."
+       named Apertis_NewSDK, proceed to the next step."
     - "Use psdk to configure the SDK to use the persistent disk:"
     - ~https://developer.apertis.org/latest/sdk-usage.html#using-the-persistent-disk-on-the-new-sdk
     - The SDK will reboot when the configuration is completed. After the reboot