Standardize testing

In order to ensure that new versions and updates to the standardized RAPID modules do not cause regressions like bugs, crashes, and performance loss, an automated test setup should be made for each module.

Suggested design:
- Each Module has a co-Module that contains all necessary code for automatically testing of the main module.
- a testing module should test that features work correctively (Gives the right result) and that processing time is as expected
- Testing modules should have as few dependencies as possible, while still fully testing the main module.
- No modules should depend on any test module - a system should be able to run completely without the test modules
- The testing module contains one procedure with the name [ModuleName]_Test with no arguments, that raises ERRORS if the test failed
- the ERROR raised is either:
- ERR_AUT_TEST_FAILED_ RESULT if the test completed with the wrong result
- ERR_AUT_TEST_FAILED_EXCEPTION if the test threw an exception while running
- ERR_AUT_TEST_FAILED_TIME if the test, or any subtest, took longer than expected