💡 [Feature]: Support debug option

[Adam-it]

🎯 Aim of the feature

Based on the problem we had in issue #278 it is not the first time that running local instance of CLI for M365, and related commands in debug, gave some answers on what could be the problem. This is some problem as the user needs to install CLI for M365 locally to make the double check which in general is not needed for this Toolkit to work.

The idea is to:

1. Add a VS Code setting to the extension, maybe a checkbox like 'run CLI commands in debug'
   

2. Setting this would add the --debug option to each CLI for M365 command and will show their output in the VS Code extension output logs. We should add the debug option when any CLI command is executed in this methods

   vscode-viva/src/services/CliCommandExecuter.ts

   Line 25 in b66d97f

   private static async tryExecuteCommand(command: string, output: string | undefined = 'text', args?: any): Promise<CommandOutput> {

[DevPio]

I would like to work on this problem