Refactor TestFrameworkConfiguration usage in sample tests and Uber tests

[nikitavlaev]

Description

Now, various check methods in our tests and processTestCases use different testFrameworkConfigurations.
That might lead to the problems in future, in example, for parametrized cases.

That change probably will require getting rid of global access of static testFrameworkConfiguration. Instead it will be supposed to be passed through various functions as a parameter, since they are not supposed to know about global states.

Expected behavior

Make usage of testFrameworkConfiguration explicit, clear and concise (as described).

Environment

Not applicable.

Potential alternatives

Leave everything as it is.

Context

Not applicable.