Browser tests: reduce timeout for instantiation to reasonable value

The timeout for browser instantiation in the browser tests has been
increased to avoid flaky tests. However, browser instantiation taking
more than 10 seconds (the previous timeout value) is an indicator for
something being wrong with the instantiation. There is no reason why
instantiation may take that long during test execution but the same
issue should never arise in productive use, thus such a case should be
captured by tests and, if necessary, be fixed productively.

In order to do so, this change reduces the test timeout value again to a
more reasonable value.

Related to
#1676

Author: HeikoKlare

bundles/org.eclipse.swt/Eclipse SWT Browser/win32/org/eclipse/swt/browser/Edge.java

@@ -465,10 +465,9 @@ private <T> void waitForFutureToFinish(CompletableFuture<T> future) {
 private static void processNextOSMessage() {
 	Display display = Display.getCurrent();
 	MSG msg = new MSG();
-	while (!OS.PeekMessage (msg, 0, 0, 0, OS.PM_NOREMOVE)) {
-		display.sleep();
+	if (OS.PeekMessage (msg, 0, 0, 0, OS.PM_NOREMOVE)) {
+		display.readAndDispatch();
 	}
-	display.readAndDispatch();
 }
 
 static ICoreWebView2CookieManager getCookieManager() {

tests/org.eclipse.swt.tests/JUnit Tests/org/eclipse/swt/tests/junit/Test_org_eclipse_swt_browser_Browser.java

@@ -296,7 +296,7 @@ private int reportOpenedDescriptors() {
 }
 
 private Browser createBrowser(Shell s, int flags) {
-	long maximumBrowserCreationMilliseconds = 90_000;
+	long maximumBrowserCreationMilliseconds = 5_000;
 	long createStartTime = System.currentTimeMillis();
 	Browser b = new Browser(s, flags);
 	// Wait for asynchronous initialization via getting URL