improvement: update the get debug-info command

* improvement: updated the get debug-info command

The old version of the command might include sensitive data in the output file.
This change introduces more explicit logging to show what's been extracted.
Changes the behaviour of the command when it comes to export data from the kubernetes cluster:
by default the command will only dump data from the garden-system and garden-system--metadata namespaces.
If the user uses the new flat --include-project, the command will dump the configuraition for the entire project as well

* fix: fixed copy for get debug-info command

* fix: improved (basic) debug info report

- added more logging in basic debug info flow
- updated glob to match debug-info-* folders
- systemInfo report format matches the one passed with --format
- added test for fixedExcludes

* fix: updated docs

* fix: improve exit on failed project config validation

docs/reference/commands.md

@@ -348,8 +348,9 @@ Outputs the status of your environment for debug purposes.
 
 Examples:
 
-garden get debug-info                # create a zip file at the root of the project with debug information
-garden get debug-info --format yaml  # output the provider info as yaml files (default as json)
+garden get debug-info                    # create a zip file at the root of the project with debug information
+garden get debug-info --format yaml      # output provider info as YAML files (default is JSON)
+garden get debug-info --include-project  # include provider info for the project namespace (disabled by default)
 
 ##### Usage
 
@@ -360,6 +361,8 @@ garden get debug-info --format yaml  # output the provider info as yaml files (d
 | Argument | Alias | Type | Description |
 | -------- | ----- | ---- | ----------- |
   | `--format` |  | `json` `yaml`  | The output format for plugin-generated debug info.
+  | `--include-project` |  | boolean | Include project-specific information from configured providers.
+Note that this may include sensitive data, depending on the provider and your configuration.
 
 ### garden init
 

garden-service/src/actions.ts

@@ -451,9 +451,9 @@ export class ActionHelper implements TypeGuard {
     return { serviceStatuses, environmentStatuses }
   }
 
-  async getDebugInfo({ log }: { log: LogEntry }): Promise<DebugInfoMap> {
+  async getDebugInfo({ log, includeProject }: { log: LogEntry, includeProject: boolean }): Promise<DebugInfoMap> {
     const handlers = this.getActionHandlers("getDebugInfo")
-    return Bluebird.props(mapValues(handlers, async (h) => h({ ...await this.commonParams(h, log) })))
+    return Bluebird.props(mapValues(handlers, async (h) => h({ ...await this.commonParams(h, log), includeProject })))
   }
 
   //endregion

garden-service/src/cli/cli.ts

@@ -322,8 +322,7 @@ export class GardenCli {
           // Other exceptions are handled within the implementation of "get debug-info".
           if (command.name === "debug-info") {
             // Use default Garden dir name as fallback since Garden class hasn't been initialised
-            await generateBasicDebugInfoReport(root, join(root, DEFAULT_GARDEN_DIR_NAME), log)
-            return
+            await generateBasicDebugInfoReport(root, join(root, DEFAULT_GARDEN_DIR_NAME), log, parsedOpts.format)
           }
           throw err
         }