Amazon Q should auto-configure as default chat provider during installation

After installing the Amazon Q extension (v1.91.0), it does not automatically become the default chat provider in VS Code. Users must manually:

1. Navigate through VS Code's settings system
2. Enable chat agents ("chat.agent.enabled": true)
3. Set appropriate request limits ("chat.agent.maxRequests")
4. Potentially modify other conflicting chat provider settings
5. Restart VS Code multiple times

This creates a poor first-time user experience and wastes developer time on configuration instead of coding.

Expected Behavior

The Amazon Q extension should either:

* Automatically configure itself as the default chat provider if no other chat extensions are active
* Prompt during installation: "Make Amazon Q your default chat provider?"
* Provide clear, one-click setup instructions in a welcome screen
* Handle conflicts with other chat providers gracefully

Current Behavior

* Extension installs successfully but chat functionality is not accessible
* No guidance provided on required configuration steps
* Users must discover and manually edit settings.json
* Conflicts with other chat extensions (like GitHub Copilot) are not resolved

Environment

* VS Code: 1.103.2
* Amazon Q Extension: 1.91.0
* OS: Windows 11

Impact

This configuration burden creates unnecessary friction for developers trying to evaluate and adopt Amazon Q, particularly when competing chat tools may have smoother setup experiences.

Beginne damit, den Installations- und First-Run-Ablauf der Amazon Q-Erweiterung nachzuverfolgen, und untersuche anschließend, wie die Chat-Einstellungen von VS Code und Konflikte mit anderen Providern derzeit behandelt werden. Als abgeschlossen gilt die Aufgabe, wenn die ausgewählte Setup-Erfahrung Amazon Q nach der Installation verfügbar macht, einen vorhandenen Provider behandelt und Benutzern klare Hinweise gibt, ohne manuelle Änderungen an den Einstellungen zu erfordern.

Vom Indexierungsmodell aus dem Issue-Text verfasst.