Move Various and TestResultsTests into UnitTests

[Garados007]

The test experiment UnitTests allows to better structure the tests and do instrumentation at the same time. Moving the Various and TestResultsTests test experiments into UnitTests allows us to get a coverage report of higher quality as if we instrument each test experiment. Doing this we also need less boilerplate code for test setup and we need less steps in the CI pipeline which also results in faster test execution.

I would only move these two test experiments into UnitTests as the other ones do test a different aspect that is difficult to do in UnitTests:

• DebugModeTests tests if the debugger works with igortests. Doing this in UnitTests needs nested RunTests execution.
• Tracing does basic tracing tests which is a requirement for UnitTests. If Tracing fails the execution of UnitTests is unreliable.
• VeryTinyTestEnvironment does test the basic setup and assertions. This is a requirement for all other test experiments.
• IMUnitTests is similar to UnitTests but tests inside an independent module. It has all the setup similar to UnitTests done.