Add a new system for testing modules

[jzethar]

This PR contains module for auto generating tests for others modules. This tool should help us to create modules faster and without any need to copy-past all the time.
The idea of the module is that we work the same as with simple block parsing, but have opportunity to generate some tests for block or transaction in the block. It does not break the test flow that was previously implemented by @Har01d only complement it.
Also the example was provided for this module. To generate it next params were used: php 3xpl.php 0 AG 40521139 A C 40521136 0x8544cc5773f307fe5319c2bbe1735771387d1287ed11b392d39187747b3ad569 S
where:

• AG -- auto generating tool
• num -- block id
• A -- all events from the block
• C -- continue test generation
• transaction -- generate tests for only this transaction from block
• S -- stop and write test file.
  All Tests will be kept in new folder Tests
  To call them in your module, you can use:

if (file_exists(__DIR__ . '/Tests/{module}Test.php'))
{
    require_once __DIR__ . '/Tests/{module}Test.php';
    $this->tests = {module}Test::$tests;
}

[alexqrid]

LGTM! Tried this new flow in #101 . It's pretty easier to add tests, than before. As this is not breaking the previous tests I believe we should merge this PR @Har01d

[Har01d]

Including

if (file_exists(__DIR__ . '/Tests/{module}Test.php'))
{
    require_once __DIR__ . '/Tests/{module}Test.php';
    $this->tests = {module}Test::$tests;
}

in every module doesn't seem to be a good solution. A better approach would be placing something like

$this->tests = true;

and processing tests in CoreModule in case of $this->tests === true.

Also, if we decide to introduce dumping data into a file in PB and others, it should be more consistent. I.e. why we do this for PB, but not for M?

[alexqrid]

Seems that backward compatibilyt is kept, is there any suggestion or let's merge this? @Har01d