## Background

Service-account keys created at the team level (no `user_id`, only `team_id`) are intended as infrastructure-level credentials — provisioned by team-admins or proxy-admins for automation, CI/CD pipelines, internal microservices, etc.

On `/key/list`, however, every regular team member is allowed to see all such service-account keys for their team. `_build_key_filter_conditions` in `litellm/proxy/management_endpoints/key_management_endpoints.py` includes them via this OR-branch:

```python if member_team_ids: # service-account keys belonging to teams the user is a member of conditions.append({ "team_id": {"in": member_team_ids}, "user_id": None, }) ```

For multi-tenant deployments this leaks the existence (and metadata) of all team-level service accounts to every regular member of the team. Members can enumerate, see aliases, budgets, expiration, and metadata of infra credentials that they don't need to know about. Team-admins and proxy-admins should retain full visibility.

## Proposed feature

Add a `general_settings.expose_team_service_accounts_to_members` boolean flag (default `true` — preserves current behavior, no breaking change).

…