Enable image input support in Amazon Q CLI for enhanced visual development workflows

### 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
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.3.2 (24D81)

### Expected behaviour

# Background
Amazon Q CLI currently lacks support for processing image inputs, limiting its ability to assist with visual development workflows.

# Problem Statement
Developers and designers cannot leverage Amazon Q CLI's capabilities for image-based tasks, such as:
- UI component generation from screenshots
- Design review assistance with diagrams
- Visual asset analysis and suggestions

# Proposed Solution
Add image input support to Amazon Q CLI to enable:
1. Direct image file processing
2. Screenshot analysis
3. Visual context understanding
4. UI component suggestions based on visual inputs

# Benefits
- Improved efficiency for UI/UX development workflows
- Enhanced collaboration between design and development teams
- Faster prototyping and iteration cycles
- Better support for visual documentation analysis

# Success Criteria
- Amazon Q CLI can accept and process image file inputs
- Support for common image formats (JPG, PNG, etc.)
- Ability to generate relevant code suggestions from visual inputs
- Integration with existing development workflows

# Implementation Considerations
- Image processing capabilities in the backend
- Security and privacy considerations for image data
- Performance impact on the CLI
- Integration with existing Amazon Q features

### Actual behaviour

Feature not supported

### Steps to reproduce

_No response_

### Environment

```yaml
[q-details]
version = "1.7.2"
hash = "b6bf5f1675dd7395009e8bc65c1145820671f211"
date = "2025-03-21T01:36:16.66764Z (6d ago)"
variant = "full"

[system-info]
os = "macOS 15.3.2 (24D81)"
chip = "Apple M1 Pro"
total-cores = 10
memory = "32.00 GB"
```

L’issue ne nomme aucun fichier, test ni point d’entrée. Commencez par localiser la gestion des entrées de la CLI et l’intégration du backend, puis clarifiez les formats d’image pris en charge, les exigences de confidentialité, les contraintes de performance et les limites du workflow. La tâche sera considérée comme terminée lorsque des fichiers image pourront être acceptés et traités pour fournir un contexte visuel et des suggestions de code pertinentes.

Rédigé par le modèle d'indexation à partir du texte de l'issue.