fix: check all required keys

[yingjiehe-xyz]

To check whether it is required key, we should check the required_keys map instead of default_keys as some keys are required and do have default value. Right now users cannot launch with ollama

Before:

After:

[lily-de]

Made a change because it wasn't playing nice with providers like openai that have a combo of optional and required params

1. Handles the special case for providers like Ollama with one key that has a default value
2. For these providers, it only considers them active if the key is explicitly set
3. For other providers, it checks that all required keys without defaults are set (e.g. OPENAI_API_KEY must be set but others for openai dont matter)

This means:

1. If OLLAMA_HOST is not explicitly set (even though it has a default), Ollama will not be considered active
2. If OLLAMA_HOST is explicitly set (as in your example where it's set in yaml), then Ollama will be considered active

The condition configStatus[key]?.is_set === true specifically checks for explicit setting, not just the existence of a default value.

[kalvinnchau]

is this Cargo.lock change related to the ui changes?

[yingjiehe-xyz]

it looks like an auto update after run just run-ui

[lily-de]

i have no idea -- i pulled main and then switched to the branch and then updated the ui and when committing saw cargo had changes too... i am confident that cargo.lock was not modified when i switched to the branch, and i think it may have happened during just run-ui during the cargo build step

[kalvinnchau]

lgtm, just a minor comment about the Cargo.lock