Changes to improve mainteinability/understability of the test cases

[augustocristian]

Upon reviewing the code for the "DeleteCourse" test, I've identified several changes that could enhance the comprehensibility of the test cases, particularly when they fail:

There are multiple instances of code duplications in certain classes, with most test cases (e.g., CourseTeacher tests) having the potential for simplification. By removing these duplications, we can centralize the root cause of flakiness into a single block of code.

Debugging videos can be challenging at times, primarily because users are not consistently initialized, and the test case name is not provided. Modifying the initialization process for each test case, such as in the eShopContainers, might be beneficial. While incorporating Selenium could be useful, I am unable to suggest an approach without simplifying the code first.

Several parts of the code can be eliminated, including some methods that return values that are not useful at all. Removing these unnecessary components will streamline the codebase

I dont want to lost the focus on the actual priority (eShopContainers) but I want to open this issue as reminder

[javiertuya]

Unassign and label because this is not priority now