test: align robotframework integration expected with full suite hierarchy

The previous expected file was generated under the bug where only the
leaf suite was reported. Now that the listener preserves the full
hierarchy from the run root, the validator receives the directory-level
"Tests" suite as data[0] and the file-level "Steps" suite as data[1],
matching the layout used by the pytest and tavern expected files.
Signatures move from "<id>::steps::<name>" to
"<id>::tests::steps::<name>" because they include every suite in order.

Author: gibiw

integration/robot/expected/robot-examples.yaml

@@ -9,7 +9,7 @@ run:
     total: 4
 results:
 - title: Test With Failing Step
-  signature: 302::steps::test_with_failing_step
+  signature: 302::tests::steps::test_with_failing_step
   testops_ids:
   - 302
   status: invalid
@@ -18,6 +18,7 @@ results:
   relations:
     suite:
       data:
+      - title: Tests
       - title: Steps
   steps:
   - data:
@@ -39,7 +40,7 @@ results:
       execution:
         status: failed
 - title: Test With Multiple Steps
-  signature: 301::steps::test_with_multiple_steps
+  signature: 301::tests::steps::test_with_multiple_steps
   testops_ids:
   - 301
   status: passed
@@ -48,6 +49,7 @@ results:
   relations:
     suite:
       data:
+      - title: Tests
       - title: Steps
   steps:
   - data:
@@ -78,7 +80,7 @@ results:
       execution:
         status: passed
 - title: Test With Single Tag
-  signature: 901::steps::test_with_single_tag
+  signature: 901::tests::steps::test_with_single_tag
   testops_ids:
   - 901
   status: passed
@@ -88,9 +90,10 @@ results:
   relations:
     suite:
       data:
+      - title: Tests
       - title: Steps
 - title: Test With Multiple Tags
-  signature: 902::steps::test_with_multiple_tags
+  signature: 902::tests::steps::test_with_multiple_tags
   testops_ids:
   - 902
   status: passed
@@ -100,4 +103,5 @@ results:
   relations:
     suite:
       data:
+      - title: Tests
       - title: Steps