[feature] Adubatl/model fetching poc

[adubatl]

📥 Pull Request

I originally wanted to be super fancy and hit a bunch of apis buuuuut then noticed litellm has built in model/provider mappings so I went to use that.

Once I got to testing a list of 500~ models was horrific, attempted to enable search but the inquirer we chose doesnt do any of that fancy stuff.

So that lead to me replacing the lib with a diff one and trying to preserve all of the flavor and soul in the existing wizard, but with a better lib for the future of the app.

📘 Description
🙏 🕯️ 🙏
We would like to take this moment to thank inquirer for their/its service.
🙏 🕯️ 🙏

Questionary seems like a more active and up to date tool, its probably overkill, but it had search yaaaay.

Its got a lot more support for robust CLI interactivity, and more importantly... it let me search a much longer model list lol.

Replaced all inquirer with questionary. There is yet another inquirer model included in the exampled poetry locks but thats not my concern just yet.

1. models are determined from the litellm package litellm.models_by_provider giving us the models in our expected format by default 🥇
2. search is enabled for the now much more thicc model list 🔍
3. a script to check that this is working is added too so you can test it and debug as we see how this works.

TODO

1. testing, the repo needs the testing love, I shant push without some tests
2. validation - the errors are handled better by questionary IMO, but I need to add custom message text

🧪 Testing
I tried one model and it worked. Ill validate more later.

[braelyn-ai]

please use uv instead of poetry

[braelyn-ai]

overall comment, i would say undo the linter changes. there's a ton of noise in this pr. if we want to make linter changes, it'd be better to apply it as a rule to the entire codebase and require it as github check (i.e. what we did with ruff). otherwise people's IDE's will be competing with each other

[braelyn-ai]

moved it out of draft to run tests

[adubatl]

I had this as a draft cause I was just messin around getting to understand the codebase - happy to close it out or take it back to my fork and play there! Don't wanna bog you down with a feature change thats just nice to have if it aint the focus.