feat: Add dry run flag to print support bundle specs to std out

[banjoh]

Description, Motivation and Context

Introduce support-bundle --dry-run flag used to print specs to stdout. The functional change is minor but I took the liberty of refactoring how we load specs from the CLI. This is where the majority of the changes lie

Fixes #1024

List of changes made

• Add a new support-bundle --dry-run cli flag
• Have the support-bundle binary load specs using LoadFromCLIArgs API, similar to the preflight binary
• Mark a number of APIs as deprecated
• Make improvements to the OCI pull implementation to handle some edge cases
• Document a few APIs

Test results

• OCI dry run

[evans] $ support-bundle --dry-run oci://registry.replicated.com/thanos-reloaded/unstable
WARN[0002] unknown type: application/vnd.unknown.config.v1+json
WARN[0003] unknown type: application/vnd.unknown.config.v1+json
apiVersion: troubleshoot.sh/v1beta2
kind: SupportBundle
metadata:
  creationTimestamp: null
  name: merged-support-bundle-spec
spec:
  collectors:
  - clusterInfo: {}
  - clusterResources: {}
  - logs:
      namespace: '{{repl Namespace }}'
      selector:
      - app=nginx
status: {}

• Local path (includes support bundle and redactor)

[evans] $ support-bundle --dry-run sample-troubleshoot.yaml
apiVersion: troubleshoot.sh/v1beta2
kind: Redactor
metadata:
  creationTimestamp: null
  name: merged-redactors-spec
spec:
  redactors:
  - fileSelector:
      file: data/my-password-dump
    name: replace password
    removals:
      values:
      - abc123
  - fileSelector: {}
    name: all files
    removals:
      regex:
      - redactor: (another)(?P<mask>.*)(here)
      - redactor: '("value": ").*(")'
        selector: S3_ENDPOINT
      yamlPath:
      - abc.xyz.*
status: {}
---
apiVersion: troubleshoot.sh/v1beta2
kind: SupportBundle
metadata:
  creationTimestamp: null
  name: merged-support-bundle-spec
spec:
  collectors:
  - clusterInfo:
      collectorName: my-cluster-info
  - clusterResources:
      collectorName: my-cluster-resources
  - http:
....

• From url

[evans] $ support-bundle --dry-run https://raw.githubusercontent.com/replicatedhq/troubleshoot/main/sample-troubleshoot.yaml
apiVersion: troubleshoot.sh/v1beta2
kind: Redactor
metadata:
  creationTimestamp: null
  name: merged-redactors-spec
spec:
  redactors:
  - fileSelector:
      file: data/my-password-dump
    name: replace password
...

• From stdin

[evans] $ cat sample-troubleshoot.yaml | support-bundle --dry-run -
apiVersion: troubleshoot.sh/v1beta2
kind: Redactor
metadata:
  creationTimestamp: null
  name: merged-redactors-spec
spec:
  redactors:
  - fileSelector:
      file: data/my-password-dump
    name: replace password
....

Checklist

• New and existing tests pass locally with introduced changes.
• Tests for the changes have been added (for bug fixes / features)
• The commit message(s) are informative and highlight any breaking changes
• Any documentation required has been added/updated. For changes to https://troubleshoot.sh/ create a PR here

Does this PR introduce a breaking change?

• Yes
• No

[CpuID]

I've started review this (on my phone) but need to finish on a computer - found a few things I want to verify

[CpuID]

LGTM at a glance but there's a failing test. once the tests are passing I'll approve 👍

[DexterYan]

by default, we have ClusterInfo and ClusterResources even without any collectors, I think maybe we don't need this check

[banjoh]

Good point. I moved that check to a different place.

support-bundle should error of there is no spec at all. Providing an empty spec should automatically add the ClusterInfo and ClusterResources collectors.

[banjoh]

LGTM at a glance but there's a failing test. once the tests are passing I'll approve 👍

Changes causing tests to fail have been made.