### Check for existing issues

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

### What happened?

### 1. Reads from wrong metadata field The endpoint reads from metadata["callback_settings"], but callbacks added via API/UI are stored in metadata["logging"]. This causes the endpoint to always return empty callbacks, even when they exist.

Example: After adding a LangSmith callback via UI, the endpoint returns empty:

``` curl -X GET 'http://localhost:4000/team/42e2f524-a89f-4153-93da-ec524a929ac1/callback' \ -H 'Authorization: Bearer sk-123' ```

Response:

``` { "status": "success", "data": { "team_id": "42e2f524-a89f-4153-93da-ec524a929ac1", "success_callbacks": [], "failure_callbacks": [], "callback_vars": {} } } ```

However, the callbacks ARE stored and visible in /team/info under metadata.logging.

### 2. Ignores YAML config Callbacks configured in `litellm_settings.default_team_settings` in `config.yaml` are completely ignored by the endpoint. There's no API endpoint or UI view that shows YAML-configured team callbacks, making it impossible to verify team callback configuration from YAML.

### 3. UI doesn't …