fix(windows): bash-safe paths for init_session and mixed MSYS paths

[xxxigm]

Summary

Follow-up to #63113 — users on upstream 7b5ba205 still hit \drivers\etc on Windows Desktop after that merge.

Root cause: #63113 only rewrote native C:\... paths in ShellFileOperations._escape_shell_arg. Two gaps remained:

• init_session / _wrap_command snapshot paths — C:\Users\...\hermes-snap-*.sh still reached bash with backslashes, so snapshot bootstrap failed every turn.
• Mixed MSYS paths — /c/Users\Alexander\Documents\... bypassed _windows_to_msys_path (no C: prefix) but still carried \U backslashes bash mangled.

This PR adds _bash_safe_path / _quote_bash_path in local.py and wires them into file_operations + base.py snapshot quoting.

Test plan

• scripts/run_tests.sh tests/tools/test_local_env_windows_msys.py tests/tools/test_file_operations.py::TestShellArgEscaping tests/tools/test_init_session_cwd_respect.py -q
• On Windows + Git Bash: write_file to C:\Users\<user>\Documents\NewTEST\readme.txt succeeds
• init_session no longer fails with snapshot bootstrap exit 1 on first tool use
• User fully quits/reopens Hermes Desktop after update before retesting

Made with Cursor

[OutThisLife]

Superseded by a scoped salvage that keeps your diagnosis and helpers, with two deltas:

1. BaseEnvironment._quote_shell_path override on LocalEnvironment instead of base.py importing from local.py (layering).
2. Explicit coverage for production C:/... snapshot paths from get_temp_dir — that's the shape users actually hit; MSYS still arg-converts C:/... during bash -l, which is why relative write_file kept failing after fix(windows): normalize native paths before bash file ops (supersedes #55481) #63113.

Closing in favor of that PR (Co-authored-by preserved). Thanks for the sharp follow-up on the Discord logs.

[OutThisLife]

Superseded — see the salvage PR linked above.