As system, whenever creating a Sub Test Execution, its results should only affect the parent requirement

As system, whenever creating a Sub Test Execution, its results should only affect the parent requirement if the separation of concerns is enabled.

Use case: when a given Test covers several "requirements", sometimes users want to run the Test "in the context of that requirement" without affecting other requirements, even though they may be linked to the same Test.

TBD: analyze if a flag/setting should exist to enable this specific behavior