TEST Acceptance test for "exceptional" mokas
TEST unit tests for exceptions in moka_call_handler
FUNCT add moka_exception

To handle our internal representation of delayed exceptions
FUNCT support symbolic throwing from moked functions
TEST check that exceptions interrupt the execution flow
FUNCT moka exceptions interrupt execution like normal exceptions
TEST simplify the requirements for exception handling

We simply rethrow any exception as it was thrown. If the exception was
unexpected, then the tests will catch it anyway
TEST change the expected behaviour for exceptions

We simply re-rise them, we want to hide the fact that the new behaviour is
running in a separate server
FUNCT Handle all exceptions equally

We transparently (almost, there is always the stack trace) transfer the
exception from the gen_server to the process calling
RESTRUCT get rid of moka_exception

It is no longer needed as we don't expose exception handling in the API, they
work transparently
RESTRUCT Delete unneeded types
RESTRUCT simplify exception handling
TEST Acceptance test for history in case of exceptions
FUNCT don't leak the internal exception wrapping in history entries

A better solution would be to create a proper ADT for history management
TEST make targets for dialyzer
FUNCT make git ignore the plt
BUGFIX fix a dialyzer warning
TEST Tighten up dialyzer
RESTRUCT prettify the Makefile

If something like a pretty Makefile is even possible
BUGFIX fix some overspecs reported by dialyzer