Add AngryGhidra-backed angr MCP tools

[rustopian]

Summary

Adds AngryGhidra-backed and direct angr/Oxidizer analysis tools to the MCP bridge while keeping AngryGhidra optional. Normal Ghidra MCP tools continue to work without AngryGhidra; AngryGhidra-specific calls return clear setup errors when it is not installed.

New / updated MCP tools

• angr_decompile_function: decompile a function with angr/Oxidizer, including Rust-oriented decompiler support and p-code language fallback where applicable.
• angr_check_setup: verify that the configured Python can import angr and optionally load the current binary.
• angr_symbolic_find: search for a symbolic path to a target address. engine="auto" prefers AngryGhidra when installed and compatible, engine="angryghidra" requires it, and engine="core" forces the direct angr helper.
• angr_annotate_symbolic_path: preview-first symbolic-path annotation. The dry run now shows each current comment that would be overwritten alongside the pending comment, returns a short-lived preview token, and refuses writes unless the exact same planned write is applied with that token.
• angr_solve_constraints_at: reach an address, apply JSON-described constraints over registers, memory, stdin, or argv, and evaluate requested values.
• angr_reachability: build an angr CFG and check static reachability between two addresses, optionally returning a path.
• angr_cfg_summary: summarize CFGFast output for a binary or function, including counts, blocks, and call sites.
• angr_callgraph_summary: summarize recovered callgraph counts and sampled call edges.
• angr_lift_block: lift a basic block to VEX, AIL, or both.
• angr_compare_decompilers: batch side-by-side Ghidra decompiler output and angr/Oxidizer output.
• angryghidra_check_setup: report the discovered AngryGhidra script and Python interpreter, or the optional-dependency error.
• angryghidra_symbolic_execute: run AngryGhidra's native symbolic execution flow with find/avoid addresses, symbolic argv, memory vectors, memory stores, registers, and hooks.
• get_comment: read the current disassembly or decompiler comment that a comment write would replace.

New / updated Ghidra HTTP endpoints

• /get_comment: read-only endpoint returning the current disassembly EOL comment or decompiler/pre comment for an address.
• Existing comment write endpoints are unchanged, but angr_annotate_symbolic_path now uses /get_comment before minting or accepting a preview token.

Safety behavior

• AngryGhidra is optional; missing installation affects only AngryGhidra-required paths.
• Symbolic execution and decompiler helper calls are bounded by limits on output size, JSON input size, symbolic input size, execution steps, summary size, lift size, and comparison batch size.
• The only angr write-capable tool is angr_annotate_symbolic_path, and it can only write comments after an exact reviewed preview token match.