## Bug: `_rotate_master_key` skips callback_vars in verification tokens & teams

### Summary

When a proxy admin rotates the master key via `POST /key/regenerate` with `new_master_key`, the `_rotate_master_key()` function in `litellm/proxy/management_endpoints/key_management_endpoints.py` re-encrypts:

1. ✅ `LiteLLM_ProxyModelTable` — litellm_params (provider API keys) 2. ✅ `LiteLLM_Config` — environment_variables 3. ✅ `LiteLLM_MCPServerTable` — credentials 4. ✅ `LiteLLM_MCPUserCredentials` — user-scoped BYOK/OAuth2 tokens 5. ✅ `LiteLLM_MCPUserEnvVars` — per-user env vars 6. ✅ `LiteLLM_CredentialsTable` — credential_values

But it does **NOT** re-encrypt:

7. ❌ `LiteLLM_VerificationToken.metadata` → `logging[*].callback_vars` (e.g. `LANGFUSE_SECRET_KEY`, `LANGSMITH_API_KEY`) 8. ❌ `LiteLLM_TeamTable.metadata` → `logging[*].callback_vars` and `callback_settings.callback_vars` 9. ❌ Config rows for `vantage_settings` / `cloudzero_settings` 10. ❌ SSO config table

After rotation, the proxy starts using the new master key for decryption but those values are still encrypted with the old key, producing the recurring error every 30 seconds:

``` Error decrypting value for key: api_key, Did …