Separate suite structural dependencies from execution information #1368

Problem or motivation

Suite structure currently mixes what belongs to what (structural dependencies) with how/when it runs (execution information).

Proposed solution

Proposing these be modelled separately to separate suite internals and execution data.

Execution data should be stored in a database table to avoid excessive memory consumption by test execution at runtime. Currently all execution data including failed expectation data is kept in-memory throughout duration of test execution. A session temporary table would probably be much better fit for purpose in this case.
Design needs to be prepared before implementation is started.

Framework area

Suite / test control