Introduce changes to assist in debugging Rancher CCG GMSA setups

[aiyengar2]

As described in #20 (comment), in a situation where a user has a misconfigured setup, identifying what needs to change and how it needs to change is fairly challenging for a non-advanced user of this feature.

This issue tracks efforts / ideas around how to make it easier to debug setups in such situations.

While this may be partially resolved by #27, the ideal fix we need here for basic users is probably something along the lines of:

• A backend tool (perhaps ccgtool, akin to promtool that can point to a Kubernetes cluster with CCG components installed and perform certain debugging operations
• Rancher UI changes to make it easier to identify if components are broken (ref: [Feature Request] add windowsOptions field in workload -> create -> pod -> securityContext UI field dashboard#9981 (comment))

This issue track the initial research to identify what a good solution would be. Feedback is welcome from users!

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.