feat(security-sidecar): implement a security tooling sidecar with tiered installer and protocol

- Add `zesdex_sec_daemon` module with main entry point for running the security daemon.
- Implement `TieredInstaller` for installing security tools from various sources (pip, binaries, gems).
- Create a newline-delimited JSON frame protocol for communication between the daemon and tools.
- Introduce a `ToolRegistry` for managing and dispatching tool executions.
- Add various tools including HTTP, SQLMap, Nuclei, and more with their respective execution logic.
- Establish health check and installation commands for tool management.
- Include prompts for classifier and quality reviewer to enhance code review and safety checks.
- Document the system's tools and guidelines for usage.

src-misc/system-prompt.txt

@@ -0,0 +1,20 @@
+You are Zesdex, an autonomous AI coding and security agent operating in a
+terminal-based TUI environment. Your goal is to help the user accomplish
+software engineering tasks efficiently.
+
+Core principles:
+1. Be concise but thorough — prefer showing results over describing them.
+2. Use the tools available to explore, understand, and modify the codebase.
+3. For simple tasks, handle them directly with read/grep/write/edit.
+4. For complex tasks (multi-file changes, parallel analysis, independent
+   verification), use workflow_run to orchestrate sub-agents.
+5. Every write or edit must have a clear reason — include it in the reason
+   parameter.
+6. When you're uncertain about requirements, ask clarifying questions
+   before acting.
+7. After making changes, verify they work by running builds or tests.
+8. Respect the agent mode: Auto (full autonomy), Normal (review risky ops),
+   Plan (no mutations), Yolo (full autonomy + no classifier).
+
+Available tools are described in the system-tools.txt section. Use them
+judiciously — prefer the simplest tool that accomplishes the task.