fix(runpod): strip pod spec before saving collected output

[xavpaice]

The runPod collector was saving the full Kubernetes Pod object (including Spec) to the bundle. Because the PodSpec can contain env vars, commands, args, volumes, and imagePullSecrets, this leaked sensitive data into the collected output.

Changes:

• In savePodDetails, copy the fetched pod and zero its Spec before JSON-marshaling.
• Refactor savePodDetails to accept kubernetes.Interface and drop the unused clientConfig parameter so the function can be unit-tested with the fake client.

Verification:

• Added TestSavePodDetails_StripsPodSpec.
• make test and make build pass.

This also affects the deprecated run collector and goldpinger, both of which delegate to CollectRunPod. Goldpinger only reads pod.Name and pod.Status.ContainerStatuses, so it remains compatible.

[greptile-apps]

_{Reviews (1): Last reviewed commit: "fix(runpod): strip pod spec before savin..." | Re-trigger Greptile}

[gilday]

Should this zero out ObjectMeta.annotations and .labels in addition to the Spec?