chore: CLI testing and maintenance

[EItanya]

The kagent CLI has quite a few awesome features, but right now it has next to no testing so it's hard to say from release to release if it's still working. We should add testing, as well as potentially design some new features for it.

[n9te9]

@EItanya
Hi! I'd love to take this on and help add tests for the CLI. It seems like a perfect way to get deeply familiar with the codebase.

I can start by establishing a testing pattern (e.g., setting up mocks for the API client and testing the standard I/O for Cobra commands) and adding coverage for some of the core commands.
Once we have a solid testing foundation in place, I'd also be very interested in discussing and designing those new features with you.

Could you assign this issue to me?

[EItanya]

Hey there, I already added quite a few additional tests in #1456, but if you are interested in adding some new CLI functionality that would be awesome!

Specifically we're interested in revamping our TUI functionality.

k9s could be a good place to get inspired

[n9te9]

@EItanya
Thanks for letting me know about #1456!

Revamping the TUI sounds like a fantastic and much more exciting challenge. I'm definitely interested in taking this on. Taking inspiration from k9s, I imagine we want interactive navigation, real-time resource watching, and vi-like keybindings.

Before writing a massive PR, how would you like to proceed?

1. Should I put together a brief design proposal (e.g., evaluating TUI frameworks like charmbracelet/bubbletea vs tview)?
2. Or would you prefer I start with a small Proof of Concept (PoC) for a specific view, like an interactive list of agents?

Let me know what works best for you!

[EItanya]

So we already have some TUI functionality build with charmbracelet/bubbletea, and in my opinion that's by far the best library for it.

A brief design proposal makes sense to me