Fix Ghostty session restore launch path

[Suda202]

Summary

• launch Ghostty sessions through the user's shell instead of injecting raw terminal input
• reuse the existing shell command builder so cwd handling matches other terminal integrations
• remove the Ghostty raw-input helpers and replace the tests with shell-command assertions

Test plan

• Set preferred terminal to Ghostty in cc-switch
• Open a Claude session terminal from the session manager
• Verify Ghostty opens directly into the resumed Claude Code session
• Confirm Terminal.app behavior is unchanged

Closes #1975

🤖 Generated with Claude Code

[yovinchen]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a179c60ca7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid shell-expanding cwd in Ghostty launch

launch_ghostty now feeds cwd through build_shell_command and runs it via -c, which turns the path into shell-parsed text (cd "..." && ...). This regresses the previous --working-directory=<dir> behavior by allowing expansions/substitutions in directory names (for example $VAR or $(...)), so a crafted or unusual project path can execute unintended commands or resolve to the wrong directory when resuming a session. Pass the working directory as a dedicated Ghostty argument (or apply shell-safe literal escaping) instead of embedding it in a shell command string.

Useful? React with 👍 / 👎.