fix: route bash apply_patch through dedicated tool and improve path/prompt handling

[Barryshen1]

This PR adds three small reliability improvements:

• Route bash apply_patch invocations through the dedicated tool — Models often run apply_patch <<'PATCH'... via the bash tool instead of calling apply_patch directly, which bypasses diff preview, write permissions, and LSP post-checks. MiMo-Code already had Patch.maybeParseApplyPatch() but it was never wired into BashTool. This PR adds maybeParseApplyPatchFromCommand() and delegates matching commands to ApplyPatchTool.

• Fix Windows memory path parsing (windows环境memory.reconcile路径正则只认正斜杠，反斜杠全部匹配失败 #861) — parsePath() and parseCcPath() used forward-slash-only regexes, causing memory reconcile to skip all files on Windows. Paths are now normalized before matching.

• Normalize CRLF in CLI --prompt input — MiMo-Code already normalized line endings for TUI paste events, but not for --prompt / piped stdin, which could garble the first message on Windows.

Test plan

• bun test test/memory/paths.test.ts — Windows backslash path cases
• bun test test/patch/patch.test.ts — maybeParseApplyPatchFromCommand cases
• bun test test/cli/prompt-text.test.ts — CRLF normalization unit tests
• bun test test/cli/tui/thread.test.ts — --prompt CRLF normalized before TUI start
• bun test test/tool/bash.test.ts — bash apply_patch heredoc routes through ApplyPatchTool and requests edit permission
• Pre-push turbo typecheck passes across all packages

Related issues

• Fixes windows环境memory.reconcile路径正则只认正斜杠，反斜杠全部匹配失败 #861 (Windows memory path parsing)
• Related to BUG Plan mode allows filesystem modifications via Bash tool #475 (plan mode bash write bypass — not addressed here, but apply_patch interception reduces one bypass vector)