Idea - kubectl-trace operator

I really like that kubectl-trace works as a standalone executable with no dependencies, and I think that's a desirable feature to keep.

Given the popularity of operators in the kubernetes community (and in our own infrastructure), I think that there is probably a good use-case for a different mode of operation for kubectl-trace that is custom-resource based.

For example, the current TraceJob struct is a nice blueprint of what a CRD for such an operator could be. The operator itself could just vendor in kubectl-trace code, and avoid duplication.

For a hackdays project, we built something very similar. One of the big draws with this is that kubect-trace doesn't have to be the only client for this - using a CR as the interface would allow for other tooling to plug into it very easily.

Start by reading the existing TraceJob struct and the kubectl-trace execution path. Compare the hackdays operator described in the issue with the repository's current Kubernetes integration and standalone executable constraints. Done means the CRD and operator scope, reuse of kubectl-trace code, and acceptance criteria are defined.

Written by the indexing model from the issue text.