Restore bounded wait in QuickAccessDialogTest to avoid bundle timeout

The wait for the dialog initialization in
testPreviousChoicesAvailableForExtension used TIMEOUT * 1000, about
83 minutes. When the dialog initialization stalls (notably on macOS),
this wait blocks far past the 1200s tycho-surefire budget for the whole
org.eclipse.ui.tests bundle, so the test runtime is killed with SIGTERM
(exit code 143) and no test results are reported for the bundle.

Restoring the wait to TIMEOUT lets the test fail fast and locally
instead of hanging and taking down the entire bundle.

See #4009

Author: vogella

tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/quickaccess/QuickAccessDialogTest.java

@@ -321,7 +321,7 @@ public void testPreviousChoicesAvailableForExtension() {
 		 * wait for the dialog initialization, to avoid race conditions later on in the test, see:
 		 * https://github.com/eclipse-platform/eclipse.platform.ui/issues/4009
 		 */
-		assertTrue(DisplayHelper.waitForCondition(text.getDisplay(), TIMEOUT * 1000,
+		assertTrue(DisplayHelper.waitForCondition(text.getDisplay(), TIMEOUT,
 				() -> dialog.infoText != null),
 				"Unexpected dialog info: " + dialog.infoText);
 		text.setText(TestQuickAccessComputer.TEST_QUICK_ACCESS_PROPOSAL_LABEL);