feat(CLI): Add non-interactive mode with template-specific CLI parameters

[monaam]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Documentation
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes
• No

The PR fulfills these requirements:

• It's submitted to the dev branch (or v[X] branch)
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• It's been tested on a Cordova (iOS, Android) app
• It's been tested on an Electron app
• Any necessary documentation has been added or updated in the docs or explained in the PR's description.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to start a new feature discussion first and wait for approval before working on it)

Other information:

Problem Statement

With the rise of AI-powered code editors and assistants (like GitHub Copilot, Cursor, Windsurf, OpenAI codex), there's a growing need for frameworks to support programmatic project creation. The current Quasar CLI's interactive-only approach creates friction when AI tools attempt to scaffold projects.

Key Benefits

1. AI Editor Integration
   Enables AI coding assistants to programmatically create Quasar projects without requiring manual user intervention, making Quasar a more attractive framework in AI-augmented development workflows.
2. Model Context Protocol (MCP) Support
   Facilitates integration with the emerging Model Context Protocol standard, allowing AI assistants to understand and generate appropriate Quasar project structures based on user requirements.
3. Automation Through Natural Language
   Users can now instruct AI assistants like "Create a Quasar app with Pinia, TypeScript, and Vite" and have the AI execute the appropriate CLI commands without additional manual steps.
4. Simplified Onboarding for AI Users
   New developers using AI assistants can get started with Quasar more quickly as their AI tools can scaffold projects for them based on their described needs.
5. Forward-Looking Framework Design
   Positions Quasar as a framework ready for the next wave of development tooling, where AI augmentation becomes increasingly central to developer workflows.
6. Extensible Parameter System
   The modular implementation makes it easy to extend for future AI integrations or API changes, ensuring Quasar remains compatible with evolving AI tool ecosystems.

This enhancement positions Quasar as a forward-thinking framework embracing the AI-assisted development paradigm, potentially increasing adoption among developers who heavily utilize these new AI coding tools.