### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate

### What happened?

`POST /team/delete` removes a team's virtual keys from the database, but it never evicts those keys from the auth cache. `/key/delete` clears cache entries after delete; team delete bypasses that path even though it already fetches `keys_to_delete` for audit persistence

A cached `UserAPIKeyAuth` short-circuits DB re-validation in `user_api_key_auth`, so a deleted team key can keep making LLM requests until TTL expiry. On multi-pod setups with Redis, that window is shared across pods

There is a second gap in the same flow: `management_endpoint_wrapper` calls `_delete_team_id_from_cache`, which deletes bare `team_id` keys while teams are stored under `team_id:{team_id}`

### Current behavior

1. Admin deletes a team via `/team/delete` 2. Keys are persisted to `LiteLLM_DeletedVerificationToken` and removed from `LiteLLM_VerificationToken` 3. Auth cache for those tokens is left intact 4. Team metadata cache under `team_id:{id}` is not cleared by the wrapper helper (wrong key format)

### Expected behavior

After a successful team delete:

1. Each …