Add logging statements declaring state of the cli_config_file_enabled

It's possible to determine this otherwise, but this makes it easier to
spot.

Author: aeisenberg

lib/analyze.js

@@ -239,6 +239,17 @@ export async function runQueries(
   }
 
   const codeql = await getCodeQL(config.codeQLCmd);
+
+  if (await util.useCodeScanningConfigInCli(codeql, featureFlags)) {
+    logger.info(
+      "Code Scanning configuration file being processed in the codeql-action."
+    );
+  } else {
+    logger.info(
+      "Code Scanning configuration file being processed in the codeql CLI."
+    );
+  }
+
   for (const language of config.languages) {
     const queries = config.queries[language];
     const queryFilters = validateQueryFilters(

lib/analyze.js.map

@@ -1705,6 +1705,9 @@ export async function initConfig(
   // happen in the CLI during the `database init` command, so no need
   // to download them here.
   if (!(await useCodeScanningConfigInCli(codeQL, featureFlags))) {
+    logger.info(
+      "Code Scanning configuration file being processed in the codeql CLI."
+    );
     const registries = parseRegistries(registriesInput);
     await downloadPacks(
       codeQL,
@@ -1715,6 +1718,10 @@ export async function initConfig(
       config.tempDir,
       logger
     );
+  } else {
+    logger.info(
+      "Code Scanning configuration file being processed in the codeql-action."
+    );
   }
 
   // Save the config so we can easily access it again in the future