Improving the Provider section and bringing OpenAI SDK into core but decoupling it from OpenAI

[Tracker]
Update Summary: Improving the Provider section and bringing OpenAI SDK into core but decoupling it from OpenAI
Short Description: Improving the Provider section and bringing OpenAI SDK into core but decoupling it from OpenAI
Check-in Date: MM/DD/YYYY
Metadata is used by the AI Tracker. Docs and additional fields here.
[/Tracker]

Problem/Motivation

Positives of current situation
Having Providers out of AI module is good for the fact that many agencies will only want to support one provider and won't want to have everything bundled.
In 1.2 we already have pulled the openai sdk into core. This means for many providers (fireworks, litelmm, olama) we only need simple config in order to get it working, almost no code.

Problems
However not having providers in core is confusing for newbies.
Having to maintain a ton of modules for each provider is getting unmanageable.
MANY providers use the OpenAI SDK and almost all the code of OpenAI, we can require it but then you have a wierd situation where the OpenAI provider is installed and visible when I don't want to use it.

Steps to reproduce (required for bugs, but not feature requests)

Please provide information like AI modules enabled, which AI provider, browser, etc.

Proposed resolution

Solution:
We could maintain a simple file inside the AI module that stores all the config needed for all the providers (Model metadata like context,
A UI for setting up "OpenAI compatible providers" which would make that provider appear in the list. (But I won't see all the other providers I could use, unless I go through the setup again).

Remaining tasks

Optional: Other details as applicable (e.g., User interface changes, API changes, Data model changes)