Improve Gemini Response Cleaning and Escaped Character Handling

[sebastianhuus]

Problem Statement: Gemini responses are not being correctly cleaned or parsed, leading to issues with escaped characters during pull request and issue generation.

Background/Context

This issue relates to existing issue #142, suggesting a recurring or related problem with how Gemini's output is processed before being used in gh commands.

Proposed Approach

There are two potential approaches to address this:

• Implement a robust Gemini response cleaner: Develop or enhance a cleaning mechanism that specifically handles escaped characters in Gemini's output, ensuring that the text is correctly formatted for gh commands.
• Investigate command rendering and parsing: Examine how gh commands are rendered and how the title and body content are parsed. It's possible that the issue lies in our parsing logic rather than Gemini's output.

Success Criteria

• Gemini-generated content (titles and bodies for PRs and issues) is correctly formatted and free of unintended escaped characters.
• The gh issue create and gh pr create commands execute successfully with clean, readable content.

🤖 Generated with Gemini CLI

[sebastianhuus]

In particular this escape sequence breaks our parser:
\"