[wptrunner] Fix override of TestharnessExecutor.create_test_window() (#54154)

It was `get_or_create_test_window()` prior to 196bcbc. This fixes
`wpt run --reuse-window`, which Chromium CI uses to speed up testing.

Author: jonathan-j-lee

tools/wptrunner/wptrunner/executors/executorchrome.py

@@ -287,7 +287,7 @@ def __init__(self, *args, sanitizer_enabled=False, reuse_window=False, **kwargs)
         self.sanitizer_enabled = sanitizer_enabled
         self.reuse_window = reuse_window
 
-    def get_or_create_test_window(self, protocol):
+    def create_test_window(self, protocol):
         test_window = self.protocol.testharness.persistent_test_window
         if test_window:
             try:
@@ -303,7 +303,7 @@ def get_or_create_test_window(self, protocol):
                 protocol.base.set_window(protocol.testharness.runner_handle)
                 test_window = self.protocol.testharness.persistent_test_window = None
         if not test_window:
-            test_window = super().get_or_create_test_window(protocol)
+            test_window = super().create_test_window(protocol)
             if self.reuse_window:
                 self.logger.info(f"Created new test window {test_window}")
             # Without `--reuse-window`, each testharness test always creates a