Added a new composite node: simple_parallel

[DarkAngelZT]

Description

Added a composite node called simple parallel. It does the same thing like the one in Unreal Engine. This node allows you to execute multiple things at the same time, e.g moving while shooting. Nested simple parallel is also supported but not suggested

Addressed issues

N/A

Screen shots

Here's debug view of my own behavior tree in Beehave debugger:

[bitbrain]

@DarkAngelZT thank you for raising this - a few things on this:

1. would you mind attaching the UE docs on this to the description of this PR? I am curious about the design decision of limiting it to exactly two child nodes
2. any new node should be covered by unit tests to ensure it works as expected. Please read the contribution guidelines for more information. I am especially curious how this behaves with nested parallel nodes or a parallel node containing other composite subtrees. Another thing we probably want to test is that interrupts work as expected.
3. the current v2.x version of beehave does not correctly test the debugger (since it is hard to test) - could you attach screenshots/gif of how the parallel node looks like inside the Beehave debugger?
4. We also would require documentation on this new composite node. So far, we only support selectors and sequence nodes. Perhaps we can introduce a new one for 'Parallel'

Generally an okay pull request - one more thing: "SimpleParallel" suggests that there could be different types of parallel, however, the architecture of Beehave V2 does not allow for other types (e.g. it assumes that always one node at a time is in RUNNING state). Could we perhaps just call it Parallel?

[DarkAngelZT]

@bitbrain Thanks for reply. Here is the official explaination of simple parallel node on epic website: https://dev.epicgames.com/documentation/en-us/unreal-engine/behavior-tree-in-unreal-engine---overview#concurrentbehaviors So basically this node has concurrency features, but it still act like a regular composite node. Which makes it different from real parallel node. As you can see its state is only controlled by first child. So I think if we simply call it parallel woud cause some misunderstanding of its feature. I will add icon and unit test later. This node is currently running in my project and I've wrote a python version for that few years ago for another engine, ant it working smoothly till now in some comercial projects, quality ensured ;)

[DarkAngelZT]

@bitbrain Unit test and docs are done, debugger screen shot has updated above. Please review

[bitbrain]

@DarkAngelZT the icon does not seem to display correctly in the debugger?

[DarkAngelZT]

@DarkAngelZT the icon does not seem to display correctly in the debugger?

That's the same code in my current project, which doesn't have icon set. here's new one: