TEST first (failing) acceptance tests for stateful mokas

We want to be able to use information about previous calls in the moka fun
DOC update the class diagram with the state requirements
TEST add an acceptance test for function call counting

We want to be able to get the past history after the execution of a moked test
DOC rewrite the notes in a better way
DOC update the class diagram with the history server

We want to hold the history of calls for each moka in a dedicated server
DOC Simple diagram for History handling

We are not representing concurrent mokas and history encapsulation. That is next step
DOC Update the moking sequence design

The moked behaviour funs ought to be evaluated in a separate process to avoid
deadlocks
DOC sequence to show the support for reentrant mokas

This shows how to avoid deadlocking.

Still not implemented, most likely current Moka deadlocks in this situation
DOC sequence for get_history calls

Two different cases:
  * Calls from behaviour funs are pruned up to they start mark
  * Calls from the test case contain the full history
DOC update the class diagram

We need a worker to evaluate funs
DOC slightly shorter sequence diagram
TEST hook in a function to get the history from a moked function

It is just returning ok, and the postcondition defaulting to false (yes this is
the same as saying it is failing ;)
TEST test call history in the postcondition

As we are just returning [] the test obviously fails
DOC added a diagram with the supervision tree

Right now the code has drifted away, MokaServer is creating the call handlers
itself
DOC update and simplify the class diagram

Removed the supervision creation hierarchy that was moved to the supervision
tree diagram