Remove hardcoding of logging and repositlories. Config options now.

[RandyChihuahua]

Configurable workspace paths and logging for the MCP host

The MCP server no longer guesses which repo it edits or where it logs — paths and log
destination come from flags or TORTOOLS_* env vars, and it prints what it resolved and
from which source on every startup. Two TOR_Core checkouts on one machine is normal, and
nothing in the output used to say which one was being written to.

--bannerlord / --tor-core / --tor-armory / --tor-environment
--log-file · --verbose, -v · --quiet · --help

Precedence: command line → environment → saved config → auto-detection, applied per path.

Behaviour changes

• Verbose logging now defaults off (was hardcoded true); --verbose restores it.
• Hardcoded debug log under C:\Program Files (x86)\Steam\... removed — dead on any
  non-C: install. The <repo>/.logs/mcp.log default is unchanged.

Worth knowing

• Found and fixed a live bug: ~15 Core services log via Console.WriteLine, which on a
  stdio server lands on the JSON-RPC channel — 54 non-JSON lines before the handshake.
  Redirected Console.Out to stderr in the host rather than touching 111 shared call sites.
• ModelContextProtocol 0.2.0-preview.2 → 2.2.0, source-compatible, no code changes.

Tested: manual, against the real workspace — both override paths, log fallback, a
deliberately wrong path, and over the wire via claude mcp add (strings_query returned
236 hits from tor_strings.xml). Existing suite passes.