### Check for existing issues

- [x] I searched open and closed issues before filing - [x] I found no issue covering cache invalidation in `/team/block` or `/team/unblock`

### What happened?

`POST /team/block` says it blocks all calls from keys with the team ID, but both the block and unblock endpoints only update Postgres

Authentication resolves teams through cache key `team_id:{team_id}` before reading the database, and `common_checks` enforces `team_object.blocked` from that cached object. If traffic has already cached `blocked=False`, calls continue after the database row is blocked until the cache expires. The inverse stale state rejects traffic after an unblock

This is inconsistent with other team mutations. The module already defines `_refresh_cached_team` and its docstring says every endpoint that mutates `litellm_teamtable` must call it so auth does not keep granting revoked permissions. The block and unblock endpoints omit that call

### Steps to Reproduce

1. Create an unblocked team and a key assigned to it 2. Send one LLM request to warm `team_id:{team_id}` 3. Call `POST /team/block` for the team 4. Confirm the database row has `blocked=True` 5. Send another reques…