[Extensions] Re-enable a test that's no longer flaky.

The ExecuteScriptApiTest.NavigationRaceExecuteScript was disabled
long ago on Windows. It should only have been disabled for Debug
builds, rather than all configurations. The related bug indicates
these tests should now be enabled.

Bug: 177163
Change-Id: Icd3aace4da8627ccc72787e57a36131b7264b603
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2158981Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: David Bertoni <dbertoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#761130}

chrome/browser/extensions/execute_script_apitest.cc

@@ -62,14 +62,7 @@ IN_PROC_BROWSER_TEST_F(ExecuteScriptApiTest, ExecuteScriptFragmentNavigation) {
   ASSERT_TRUE(RunExtensionTest(extension_name)) << message_;
 }
 
-// Fails often on Windows dbg bots. http://crbug.com/177163
-#if defined(OS_WIN)
-#define MAYBE_NavigationRaceExecuteScript DISABLED_NavigationRaceExecuteScript
-#else
-#define MAYBE_NavigationRaceExecuteScript NavigationRaceExecuteScript
-#endif  // defined(OS_WIN)
-IN_PROC_BROWSER_TEST_F(ExecuteScriptApiTest,
-                       MAYBE_NavigationRaceExecuteScript) {
+IN_PROC_BROWSER_TEST_F(ExecuteScriptApiTest, NavigationRaceExecuteScript) {
   ASSERT_TRUE(RunExtensionSubtest("executescript/navigation_race",
                                   "execute_script.html")) << message_;
 }