Fix LLM/MCP Configuration not rehydrated after DB reload

Description

When LLM Provider, LLM Proxy, or MCP configurations are loaded from the database (e.g., after controller restart), unmarshalSourceConfig in sql_store.go only populates SourceConfiguration, leaving Configuration as a zero-value api.APIConfiguration. Multiple code paths depend on Configuration.Spec.AsAPIConfigData() and break silently.

Affected code paths:

1. matchesFilters (llm_deployment.go:829) — ListLLMProviders() / ListLLMProxies() with filter parameters (displayName, version, context, vhost) silently return empty results because AsAPIConfigData() errors and matchesFilters returns false for every config.

2. translateAPIConfig (translator.go:466) — TranslateConfigs() iterates all configs including LLM/MCP. Since Configuration.Kind is zero-value, LLM/MCP configs fall through to translateAPIConfig() which fails on the zero-value Spec. xDS snapshots for these APIs are missing after restart.

3. transformProxy (llm_transformer.go:109) — Deploying a new LLM proxy after restart fails because the referenced provider's Configuration.Spec.AsAPIConfigData() returns an error when reading vhost info.

Root cause:

In pkg/storage/sql_store.go unmarshalSourceConfig(), the RestApi/WebSubApi cases set both cfg.SourceConfiguration and cfg.Configuration, but the LlmProvider, LlmProxy, and Mcp cases only set cfg.SourceConfiguration.

Fix:

After setting SourceConfiguration for each LLM/MCP kind, rehydrate Configuration by building a minimal api.APIConfiguration with basic metadata (DisplayName, Version, Context, Vhosts, Upstream) derived from the source config — mirroring what the transformers produce at deployment time.

Version

No response

Related Issue

No response

Start in pkg/storage/sql_store.go at unmarshalSourceConfig and compare the LlmProvider, LlmProxy, and Mcp cases with RestApi and WebSubApi. Trace the affected paths in llm_deployment.go, translator.go, and llm_transformer.go, then verify that filters, TranslateConfigs, and new LLM proxy deployment work after a database reload.