After the CE UI-tests have been cleaned-up we should do the same for the EE UI-tests.

Part of that cleanup effort should be at least:

• Remove AbstractMagnoliaEEUITest.setDefaultDriverTimeout()
• Clean up errors from previous point: solve issues after setting implicitlyWait to zero
  • Use proper wait untils/assert eventually in dynamic contexts
• Remove AbstractMagnoliaEEUITest.appIsLoaded() and replace inappropriate uses (see MGNLCE-88)
• Extract conditions and locators into the base classes in the CE bundle

General Tip: Write and optimize the tests in a way so that they are not EE specific. Meaning they should not rely on the Abstract EE UI Test class, they should not have EE only helper classes, etc