[CLI] Organize Debug CLI

[dylanlott]

Objective

Organize the debug CLI sub commands into logical groups of responsibility and refactor the Viper CLI to handle it cleanly while still respecting the interactive prompt.

Origin Document

#664 connected the terminal prompt and the debug CLI sub commands together for testing purposes by building out the Viper CLI sub commands programmatically.

Goals

• Organize the debug CLI for developer experience

Deliverable

• [ ] CLI with organized debug CLI sub commands
• [ ] Interactive debug prompt maintained

Non-goals / Non-deliverables

• Breaking the interactive prompt
• Having to write the same function twice to maintain sub commands.

General issue deliverables

• [ ] Update the appropriate CHANGELOG(s)
• [ ] Update any relevant local/global README(s)
• [ ] Update relevant source code tree explanations
• [ ] Add or update any relevant or supporting mermaid diagrams

Testing Methodology

• [ ] Task specific tests or benchmarks: make ...
• [ ] New tests or benchmarks: make ...
• [ ] All tests: make test_all
• [ ] LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md
• [ ] k8s LocalNet: verify a k8s LocalNet is still functioning correctly by following the instructions here

---

Creator: [github username of the creator] Co-Owners: [optional - github usernames of the co-owner(s)]