Add screenshots and arbitration graphs to the tutorial pages

docs/tasks/1_implement_behavior_component.md

@@ -8,6 +8,10 @@ tagline: "Task 1: Implement a Behavior Component"
 
 Implement your first `checkInvocationCondition()` and `getCommand()` function, such that the ChaseGhost behavior component passes its unit tests.
 
+<p align="center">
+  <img src="../assets/img/tutorial_scenario_ChaseGhost_cropped.png" width="300" /> 
+</p>
+
 ## Context
 
 Before we start building our arbitration graph, we want to take a closer look into behavior components.

docs/tasks/2_extend_arbitration_graph.md

@@ -76,6 +76,13 @@ explicit PacmanAgent(const entt::Game& game)
     rootArbitrator_->addOption(moveRandomlyBehavior_, PriorityArbitrator::Option::Flags::INTERRUPTABLE);
 }
 ```
+
+Your arbitration graph should now look like this:
+
+<p align="center">
+  <img src="../assets/img/tutorial_arbitrator_ChaseGhost.png" width="500" />
+</p>
+
 </details>
 
 

docs/tasks/3_nested_arbitrators.md

@@ -8,6 +8,8 @@ tagline: "Task 3: Nested arbitration graphs"
 
 Integrate a long-term behavior and add another layer to the arbitration graph.
 
+![](../assets/img/tutorial_arbitrator_EatDotsRandomly.png)
+
 ## Context
 
 We have now implemented a behavior component and integrated it into the arbitration graph.

docs/tasks/4_cost_arbitration.md

@@ -8,6 +8,8 @@ tagline: "Task 4: Arbitrate based on predicted utility"
 
 Learn how the cost arbitrator can help you to arbitrate between behaviors based on their expected cost/utility.
 
+![](../assets/img/tutorial_arbitrator_EatDotsByReward.png)
+
 ## Context
 
 The `EatDot` arbitrator we added in the [previous task](3_nested_arbitrators.md) decides between the two dot eating strategies randomly.

docs/tasks/5_verification.md

@@ -8,6 +8,8 @@ tagline: "Task 5: Better safe than sorry"
 
 Execute only safe commands and add a fallback strategy.
 
+![](../assets/img/tutorial_arbitrator_verification.png)
+
 ## Context
 
 The arbitration graph is now complete and Pac-Man is eating dots like a pro.