Add support for Warp Terminal integration

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue

### Operating system

macOS 15.5.0 (24F74)

### Expected behaviour

Amazon Q CLI should work seamlessly with Warp Terminal, including all terminal integration features.

### Actual behaviour

Running `q doctor` shows "WarpTerminal is not supported" error, and terminal integration features don't work properly. Fish shell configuration files also had permission issues that required `sudo q debug fix-permissions` to resolve.

```
[chat-transcript]
> Error: fish (/Users/luronghua/.config/fish/conf.d/00_fig_pre.fish): Permissions denied for /Users/luronghua/.config/fish/conf.d>
>
To automatically fix the permissions run: sudo q debug fix-permissions>
>
Error: Permission denied (os error 13)>
>
>
>
fish (/Users/luronghua/.config/fish/conf.d/99_fig_post.fish): Permissions denied for /Users/luronghua/.config/fish/conf.d>
>
To automatically fix the permissions run: sudo q debug fix-permissions>
>
Error: Permission denied (os error 13)

I can see you're encountering permission issues with Fish shell configuration files in your `~/.config/fish/conf.d/` directory. The error messages suggest that the Q CLI has a built-in command to fix these permissions.

Let me help you resolve this by running the suggested fix:
[Tool uses: execute_bash]

> t

Great! The permissions have been fixed successfully. The command corrected the ownership for various shell configuration files including your bash and zsh profiles.

The permission issues you were seeing with the Fish shell configuration files (`00_fig_pre.fish` and `99_fig_post.fish`) should now be resolved. These files are typically created by Q CLI for shell integration.

If you continue to experience any issues, you can:
1. Run `q doctor` to diagnose any remaining problems
2. Use `q issue` to report persistent issues

Try opening a new terminal session or restarting your Fish shell to see if the errors are gone.
[Tool uses: none]

> q doctor

[Tool uses: execute_bash]

The `q doctor` command found an issue: **WarpTerminal is not supported** for Amazon Q terminal integrations.

It looks like you're using Warp Terminal, which currently isn't supported by Amazon Q's terminal integration features. This explains why you might be experiencing some configuration issues.

Here are your options:

1. **Continue using Warp Terminal**: You can still use Q CLI commands, but some terminal integration features may not work properly.

2. **Switch to a supported terminal**: Consider using a supported terminal like:
- Terminal.app (macOS default)
- iTerm2
- VS Code integrated terminal
- Other standard terminals

3. **Report the issue**: If you'd like Warp Terminal support added, you can report this as a feature request:
\```bash
q issue
\```

The permission fixes we applied earlier should still help with the Fish shell configuration files, but the terminal integration features may remain limited while using Warp Terminal.

Would you like me to help you with anything else, or would you prefer to report this as an issue for potential future Warp Terminal support?
[Tool uses: none]

> q issue

[Tool uses: execute_bash]

The `q issue` command failed because it's not running in a proper terminal environment. This command typically opens an interactive interface or browser to report issues.

Since you're experiencing the Warp Terminal compatibility issue, I can help you report this through the GitHub issue reporting tool instead:
[Tool uses: report_issue]
```

### Steps to reproduce

1. Install Amazon Q CLI on macOS
2. Use Warp Terminal as the default terminal
3. Run `q doctor`
4. Observe the "WarpTerminal is not supported" error