### What happened?

Bug: Updated fallback configuration not reloaded on redeploy

## Summary When redeploying an existing LiteLLM setup with updated configuration, changes in the fallbacks section are not applied unless manually updated via the LiteLLM API.

## Details After adding a new model (claude-4-5-sonnet) along with its fallback configuration, the changes were correctly applied in our validation environment (which is deployed from scratch). However, in development and production environments, where the infrastructure already existed, the updated fallback configuration was not reflected after redeployment. The previous fallback mappings remained active until I manually reconfigured them in the UI.

## Expected behavior LiteLLM should detect and apply changes to the fallback configuration (fallbacks) on redeploy, even when the infrastructure already exist (database).

## Actual behavior Redeploying LiteLLM with an updated config does not refresh the fallback section for existing environments.

## Reproduction steps

- Deploy LiteLLM with an initial fallback configuration. - Update the config file to include a new model and fallback mapping. - Redeploy the application (without…