Add MCP (Model Context Protocol) Support to Ignite CLI

**Summary**
I would like to request support for MCP (Model Context Protocol) integration in Ignite CLI to enable better AI-assisted development workflows for React Native projects.

**Motivation**
MCP is an open protocol that standardizes how AI assistants interact with development tools and codebases. Adding MCP support to Ignite would:

- Enable AI assistants to better understand Ignite project structure and conventions
- Provide contextual assistance for Ignite-specific patterns (screens, components, models, etc.)
- Improve code generation and suggestions that align with Ignite's opinionated architecture
- Streamline the development workflow when using AI coding assistants

**Proposed Solution**

- Implement MCP support through one or more of the following approaches:
-
- MCP Server Integration: Create an MCP server that can expose Ignite project structure and metadata
- Generator Integration: Allow MCP clients to trigger Ignite generators programmatically
- Context Provider: Provide project context to MCP clients about:
1. Current Ignite version and boilerplate structure
2. Available generators and their usage
3. Project-specific configurations and conventions
4. Navigation structure and screen organization

**Use Cases**

- AI assistants understanding Ignite folder structure and naming conventions
- Automated code generation that follows Ignite patterns
- Context-aware suggestions for navigation, state management, and component architecture
- Integration with AI-powered development tools that support MCP

No files, tests, or entry points are named. Start by reviewing the Ignite CLI and its generator interfaces, then determine whether MCP server integration, generator integration, or a project context provider is the intended scope. Done should include a defined MCP approach covering the listed Ignite project metadata and workflows.

Written by the indexing model from the issue text.