[BUG] Mixing models between configuration profiles

[ante-maric]

Problem (one or two sentences)

When two configuration profiles are created, both with LiteLLM API provider but different instances (different base url), list of models are not always pulled from currently selected one, causing an issue when they don't provide the same models (The model ID (some-model) you provided is not available. Please choose a different model.).

Context (who is affected and when)

Happens to everyone that needs to use multiple configuration profiles with different LiteLLM instances (possibly this happens for other providers too).

Reproduction steps

1. Add two configuration profiles that use LiteLLM provider but different instances (base url) with different models
2. Switch between profiles and try to refresh models
3. Model list is always pulled from one of the providers which isn't necessarily currently selected one.

Expected result

Configuration profiles are independent and getting list of models uses API provider from currently selected configuration profile.

Actual result

List of models is not always pulled from API provier that is configured for the currenly selected configuration profile.

Variations tried (optional)

No response

App Version

v3.31.0

API Provider (optional)

LiteLLM

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I'm exploring a potential fix for the configuration profile model mixing issue and will open a PR to share progress.

[roomote]

Opened a PR with my attempt at addressing this issue: #9170. Feedback welcome!

[ante-maric]

Is this going to get some attention any time soon? I was impressed with how fast PR was opened by the bot, but it seems that doesn't make bugs get fixed sooner.

[hannesrudolph]

@roomote can you please rescope this and make a new PR?