fix: Avoid auto-reload for recently created source directory

Watchpack has a bug that caused it to dispatch change events for files
that were created recently (up to 2 seconds before now). This can
trigger an unwanted auto-reload, e.g. in the scenario of an extension
developer building an extension and using `web-ext run` to immediately
launch that built package.

Fixing this bug caused test.cli.run-target-chromium.js to time out
because the "with auto-reload" test got stuck, because it waited until
"The extension will reload if any source file changes" was logged before
writing a file to trigger auto-reload, but that message was logged
before the watcher was registered. To fix that test issue, move the
logging after initializing the reload strategy.

Author: Rob--W

src/cmd/run.js

@@ -206,8 +206,6 @@ export default async function run(
   if (noReload) {
     log.info('Automatic extension reloading has been disabled');
   } else {
-    log.info('The extension will reload if any source file changes');
-
     reloadStrategy({
       extensionRunner,
       sourceDir,
@@ -217,6 +215,8 @@ export default async function run(
       ignoreFiles,
       noInput,
     });
+
+    log.info('The extension will reload if any source file changes');
   }
 
   return extensionRunner;