Improve stability of Selenium tests

[Avery-Dunn]

Attempts to resolve some of the flaky tests described in #5357

One of the most common failure occurs during interactive tests, occasionally there's a timeout when trying to create the web driver for Selenium:

Test method Microsoft.Identity.Test.Integration.SeleniumTests.InteractiveFlowTests.Interactive_AADAsync threw exception:
OpenQA.Selenium.WebDriverException: The HTTP request to the remote WebDriver server for URL http://localhost:52547/session timed out after 120 seconds.

Stack trace
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at OpenQA.Selenium.Remote.HttpCommandExecutor.<MakeHttpRequest>d__36.MoveNext()
--- End of stack trace from previous location where exception was thrown ---

// ...


at OpenQA.Selenium.Chrome.ChromeDriver..ctor(String chromeDriverDirectory, ChromeOptions options)
[at Microsoft.Identity.Test.Integration.Infrastructure.SeleniumExtensions.CreateDefaultWebDriver() in /_/tests/Microsoft.Identity.Test.Integration.NetCore/Infrastructure/SeleniumExtensions.cs:line 41](https://identitydivision.visualstudio.com/IDDP/_git/9a0dc2f2-2cc8-42ef-a2af-2b659b9c4530?path=%2F_%2Ftests%2FMicrosoft.Identity.Test.Integration.NetCore%2FInfrastructure%2FSeleniumExtensions.cs&version=GBmain&_a=contents&line=41&lineEnd=42&lineStartColumn=1&lineEndColumn=1&lineStyle=plain)
[at Microsoft.Identity.Test.Integration.Infrastructure.SeleniumWebUI.InitDriverAndGoToUrl(String url) in /_/tests/Microsoft.Identity.Test.Integration.NetCore/Infrastructure/SeleniumWebUI.cs:line 95](https://identitydivision.visualstudio.com/IDDP/_git/9a0dc2f2-2cc8-42ef-a2af-2b659b9c4530?path=%2F_%2Ftests%2FMicrosoft.Identity.Test.Integration.NetCore%2FInfrastructure%2FSeleniumWebUI.cs&version=GBmain&_a=contents&line=95&lineEnd=96&lineStartColumn=1&lineEndColumn=1&lineStyle=plain)
[at Microsoft.Identity.Test.Integration.Infrastructure.SeleniumWebUI.<SeleniumAcquireAuthAsync>d__10.MoveNext() in /_/tests/Microsoft.Identity.Test.Integration.NetCore/Infrastructure/SeleniumWebUI.cs:line 104](https://identitydivision.visualstudio.com/IDDP/_git/9a0dc2f2-2cc8-42ef-a2af-2b659b9c4530?path=%2F_%2Ftests%2FMicrosoft.Identity.Test.Integration.NetCore%2FInfrastructure%2FSeleniumWebUI.cs&version=GBmain&_a=contents&line=104&lineEnd=105&lineStartColumn=1&lineEndColumn=1&lineStyle=plain)

This PR attempts to improve the stability of the webdriver creation by implementing some simple retry behavior, and giving it a much shorter timeout period before it gives up and tries again.

This should reduce the number of failed pipeline runs, and overall make the interactive tests run a bit quicker.

[neha-bhargava]

Have you tried to run this PR through one branch build? If not, I would recommend running it before merging this PR.

[Avery-Dunn]

Have you tried to run this PR through one branch build? If not, I would recommend running it before merging this PR.

Yeah, if you look at the run history around June 25-26 you'll see a bunch of manual runs by me. Here's an example, and after about 10 runs I didn't see the flaky tests fail: https://identitydivision.visualstudio.com/IDDP/_build/results?buildId=1498688&view=results