Refactor scenario behaviour trees
User Story/Description
As a developer it would be great if the behaviour trees are divided into more sub-tree primitives so that it is easier to construct new behaviour trees for scenarios. I.e. that asking for someones name, confirming and saving it is done in one sub-tree.
Definition of Done
When we have more behaviour tree primitives to use.
How
Look at the current *.tree files and pick out parts to create a new .tree file for (make sure to check how the .tree to python script works so that subtrees are properly implemented in it's place)