Feature Request: UI to allow users to manage different AI models

[Jacksonmills]

Summary:
Improve the UI to allow users to manage different AI models and configure corresponding API keys from the settings. Add a dropdown menu in the main chat interface for seamless switching between active models. Integrate persistent storage options to save these configurations.

Problem:
Currently, there is no integrated method for users to manage multiple AI models and their respective API keys within the application settings, nor a mechanism to persist these settings for future use. Users also need a convenient way to switch between active models directly from the chat interface.

Solution:

1. Develop modals in the settings section for model and API key management, allowing users to add, configure, or remove models and their API keys.
2. Implement a dropdown menu in the chat interface to switch between configured models easily.

Design:

• Modals within the settings for AI model and API key management.
• Dropdown menu in the chat interface for active model selection.
• Consistent and intuitive UI design that aligns with the current interface standards.

Persistent Storage Solutions:

• Integrate Capacitor for local storage of model configurations and API keys.
• Provide an option for cloud-based storage with Supabase for users who prefer to sync their settings across devices.
• Ensure that storage of sensitive information like API keys is secure and encrypted.

User Stories:

• As a user, I want to manage different AI models and API keys within the settings, and have these settings persist across sessions.
• As a user, I want to switch between configured models quickly from the chat interface for different tasks and comparisons.

Acceptance Criteria:

• Users can add, configure, and remove AI models and API keys within the settings modals.
• The dropdown menu allows for quick switching of active models in the chat.
• Model configurations and API keys are securely stored and persist across sessions and devices.

[Jacksonmills]

@adamcohenhillel feel free to edit the issue if anything needs better explained. I think I will get started on this and we can figure out the best way to persist the settings in the process (not sure the best route for that will be)