worker: spawn under the IDA python (has ida_pro_mcp), not the TUI's

Root cause of "ModuleNotFoundError: No module named 'ida_pro_mcp'": the worker was
spawned with sys.executable — the TUI's python (~/ida-venv) which has idalib +
textual but NOT ida_pro_mcp. The package split on this box:
    /usr/bin/python   : idapro + ida_pro_mcp   (the "IDA python")
    ~/ida-venv/python : idapro + textual        (the "TUI python", runs the app)

Fix: WorkerClient now auto-detects a python that can import ida_pro_mcp
(IDATUI_WORKER_PYTHON override, else /usr/bin/python[3], else sys.executable) and
runs worker.py as a SCRIPT rather than `-m idatui.worker`, so it doesn't import
the textual-dependent idatui package __init__ under a python that has no textual.
worker.py itself is pure stdlib at load; idapro/ida_pro_mcp are imported at
runtime (both present in the IDA python).

Verified: detection returns /usr/bin/python; worker.py loads clean there.

0 files changed, 0 insertions, 0 deletions