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/app/workflow/engine.rs

@@ -110,29 +110,8 @@ pub fn run_workflow(script: &WorkflowScript, args: &HashMap<String, String>) ->
     Ok("workflow completed".to_string())
 }
 
-#[expect(dead_code)]
-pub fn push_finding(engine: &mut WorkflowEngine, text: &str) {
-    engine.findings.push(text.to_string());
-}
-
 pub fn note_finding(text: &str) {
     if let Ok(mut findings) = FINDINGS.lock() {
         findings.push(text.to_string());
     }
 }
-
-#[expect(dead_code)]
-pub fn current_findings() -> Vec<String> {
-    if let Ok(findings) = FINDINGS.lock() {
-        findings.clone()
-    } else {
-        Vec::new()
-    }
-}
-
-#[expect(dead_code)]
-pub fn clear_findings() {
-    if let Ok(mut findings) = FINDINGS.lock() {
-        findings.clear();
-    }
-}