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"
```

El issue no indica archivos, pruebas ni puntos de entrada. Empieza por localizar la gestión de entrada de la CLI y la integración con el backend, y después aclara los formatos de imagen compatibles, los requisitos de privacidad, las restricciones de rendimiento y los límites del flujo de trabajo. La tarea estará completa cuando se puedan aceptar y procesar archivos de imagen para proporcionar contexto visual y sugerencias de código relevantes.

Escrito por el modelo de indexación a partir del texto del issue.