BrowserWebDriverContainer: Timeout in containerIsStarted

[Flugtiger]

We get a timeout in BrowserWebDriverContainer#containerIsStarted. It seems the fix for #373 is broken. The inner getWithTimout contains a double nested lambda so the timeout is only applied to the outer lambda which returns immediatly. So when "new RemoteWebDriver" gets stuck in the race condition mentioned in #373, retryUntilSuccess throws when it reaches its own timeout in the first try.

[rnorth]

@Flugtiger is it possible that you're encountering this? SeleniumHQ/docker-selenium#1346

#4315 is a workaround which we should be releasing soon - I'm not sure whether this has been fixed on the selenium side as well.