#2476 Get episode schedule working

src/primaite/config/_package_data/scenario_with_placeholders/greens_1.yaml

@@ -1,5 +1,5 @@
 greens: &greens
-  - ref: green_client_2
+  - ref: green_A
     team: GREEN
     type: ProbabilisticAgent
     agent_settings:
@@ -48,7 +48,7 @@ greens: &greens
           options:
             node_hostname: client_2
 
-  - ref: green_client_1
+  - ref: green_B
     team: GREEN
     type: ProbabilisticAgent
     agent_settings:

src/primaite/config/_package_data/scenario_with_placeholders/greens_2.yaml

@@ -1,5 +1,5 @@
 greens: &greens
-  - ref: green_client_2
+  - ref: green_C
     team: GREEN
     type: ProbabilisticAgent
     agent_settings:

src/primaite/config/_package_data/scenario_with_placeholders/reds_1.yaml

@@ -1,5 +1,5 @@
 reds: &reds
-  - ref: attacker_1
+  - ref: red_A
     team: RED
     type: RedDatabaseCorruptingAgent
 

src/primaite/config/_package_data/scenario_with_placeholders/reds_2.yaml

@@ -1,5 +1,5 @@
 reds: &reds
-  - ref: attacker_2
+  - ref: red_B
     team: RED
     type: RedDatabaseCorruptingAgent
 

src/primaite/config/_package_data/scenario_with_placeholders/scenario.yaml

@@ -23,7 +23,6 @@ game:
 agents:
   - *greens
   - *reds
-  - *blue(s)
 
   - ref: defender
     team: BLUE

src/primaite/config/_package_data/scenario_with_placeholders/schedule.yaml

@@ -1,17 +1,17 @@
 base_scenario: scenario.yaml
 schedule:
   0:
-    green: greens_1.yaml
-    red: reds_1.yaml
+    - greens_1.yaml
+    - reds_1.yaml
   1:
-    green: greens_1.yaml
-    red: reds_2.yaml
+    - greens_1.yaml
+    - reds_2.yaml
   2:
-    green: greens_2.yaml
-    red: reds_1.yaml
+    - greens_2.yaml
+    - reds_1.yaml
   3:
-    green: greens_2.yaml
-    red: reds_2.yaml
+    - greens_2.yaml
+    - reds_2.yaml
 
 # touch base with container to see what they've implemented for training schedule and evaluation schedule - for naming convention consistency
 # when you exceed the number of episodes defined in the yaml, raise a warning and loop back to the beginning