fix(bulk-operations): use console-log policy for catch() error visibility

Post-merge, the console-log state moved from configHandler.get('log').
showConsoleLogs to the process-wide console-policy module, and the
configHandler import was dropped. catch() still referenced configHandler,
breaking the build (TS2304).

Switch the guard to isConsoleLogEnabled() so the friendly error line still
prints on failure when console logs are off, without double-printing when
they are on. Matches the convention the rest of the file now follows.

Ref: DX-10224

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: harshitha-cstk

packages/contentstack-bulk-operations/src/base-bulk-command.ts

@@ -11,6 +11,7 @@ import {
   getChalk,
   loadChalk,
   CLIProgressManager,
+  isConsoleLogEnabled,
 } from '@contentstack/cli-utilities';
 
 import config from './config';
@@ -656,13 +657,12 @@ export abstract class BaseBulkCommand extends Command {
     // For other errors, use the CLI utilities error handler
     handleAndLogError(error);
 
-    // handleAndLogError only reaches the console when log.showConsoleLogs is enabled
+    // handleAndLogError only reaches the console when the console-log policy is enabled
     // (the winston error transport is silenced otherwise), so a failure would leave the
     // terminal completely silent when the user has console logs turned off. Print a
     // user-facing error line here to fill that gap, guarded so we don't double-print when
     // console logs are on and handleAndLogError already emitted the error.
-    const showConsoleLogs = Boolean(configHandler.get('log')?.showConsoleLogs);
-    if (!showConsoleLogs) {
+    if (!isConsoleLogEnabled()) {
       const errorMessage = cliErrorHandler.classifyError(error)?.message || error?.message || 'Unknown error';
       cliux.print(`Error: ${errorMessage}`, { color: 'red' });
     }