Switch selenium tests to use implicitly_wait() instead of custom wait functions.

[Tim Graham]

From the selenium docs, "Dependent on several factors, including the OS/Browser combination, WebDriver may or may not wait for the page to load. In some circumstances, WebDriver may return control before the page has finished, or even started, loading. To ensure robustness, you need to wait for the element(s) to exist in the page using ​Explicit and Implicit Waits."

Currently, we have a collection of ​wait_for* methods to accomplish this. The idea is to switch our code to call self.selenium.implicitly_wait(10) after initializing self.selenium which should allow us to remove many of these waiting calls.

[Tim Graham <timograham@…>]

In b2cddeaa:

Refs #26048 -- Fixed a flaky i18n selenium test: test_javascript_gettext.

[Tim Graham]

​PR. Unfortunately, I think we still need to keep some waits after actions like clicks if they aren't followed by other selenium queries.

[Florian Apolloner]

That is not so unfortunate, at least now we should be able to know when to add them ;)

[Tim Graham <timograham@…>]

In 294d0d8:

Fixed #26048 -- Made admin selenium tests use implicitly_wait()

[Tim Graham <timograham@…>]

In 3486311:

Refs #26048 -- Fixed a flaky selenium test.