Fix kubectl_get returning wrong pod status (e.g. Running instead of CrashLoopBackOff)

[Flux159]

Summary

• Fix kubectl_get reporting incorrect pod status (e.g. "Running" instead of "CrashLoopBackOff")
• Add getPodStatus() function that mirrors kubectl's own status computation logic from pkg/printers/internalversion/printers.go
• Inspects container statuses (state.waiting.reason, state.terminated.reason), init container statuses, and pod deletion timestamps to derive the human-friendly status

Background

Previously, getResourceStatus() only returned pod.status.phase, which is the pod lifecycle phase (Running, Pending, Succeeded, Failed, Unknown). This doesn't reflect container-level statuses like CrashLoopBackOff, ImagePullBackOff, OOMKilled, Error, etc. A pod can have phase: Running while its container is in CrashLoopBackOff.

This was first identified in PR #130 which renamed status to phase to be more semantically accurate, but the underlying problem of not showing container-level statuses remained. Issue #273 reports the same problem in the current kubectl CLI-based implementation.

Test plan

• Verify that pods in CrashLoopBackOff state show "CrashLoopBackOff" instead of "Running"
• Verify that pods in ImagePullBackOff state show "ImagePullBackOff"
• Verify that normally running pods still show "Running"
• Verify that terminated pods show appropriate exit code/signal status
• Verify that pods with failing init containers show "Init:" prefixed status
• Verify that pods being deleted show "Terminating"
• Run bun run build to confirm clean build

Fixes #273

🤖 Generated with Claude Code

[rr-paras-patel]

LGTM