Arbitrary secret key refs and templating in collectors

[NoaheCampbell]

Description, Motivation and Context

Enable collectors that require sensitive connection details, like passwords and TLS certs, without embedding them in specs, unlocking DB diagnostics in production clusters.

Based off of this issue:
https://github.com/replicated-collab/cohere-replicated/issues/48

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

[NoaheCampbell]

As an example, you can create a cluster using the replicated CLI and run

kubectl apply -f troubleshoot/test-v1beta3-secret.yaml

to apply the secrets there, and then run

support-bundle troubleshoot/test-v1beta3-bundle.yaml

which will generate a support bundle with the following files and content

postgres-with-secret.json

{"isConnected":false,"error":"failed to connect to `user=testuser database=testdb`: hostname resolving error: lookup postgres.example.com on 192.168.86.1:53: no such host"}

[bennyyang11]

There are a few TODOs here. Are these needed at all.

[NoaheCampbell]

The structs are needed as there was a problem with how v1beta3 was loaded previously, since it wasnt using the loader like v1beta2 was apparently, and adding a lot of fields here would take a lot of extra time to do and test and be too much of a branch for this PR so I left them as TODOs after confirming it still behaves the same

[bennyyang11]

Sounds good

[bennyyang11]

Looks good to me