### Check for existing issues

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

### What happened?

`GET /v2/user/info` is intended to be the lightweight replacement for `/user/info`, excluding virtual keys and full team objects while returning the user's own profile data.

The user database row already contains `rpm_limit` and `tpm_limit`, and the endpoint's existing `find_unique` query retrieves them. However, `UserInfoV2Response` does not declare either field, and the endpoint's explicit response mapping drops both values.

As a result, clients that need the complete user-level rate-limit policy must continue calling the heavier `/user/info` endpoint.

Expected behavior: `/v2/user/info` returns the user's optional `rpm_limit` and `tpm_limit` values without adding any database queries or returning keys/full team objects.

Actual behavior: both fields are absent from the JSON response even when they are set on the user row.

### Steps to Reproduce

1. Start a live LiteLLM proxy at commit `817582e697c92a67f8bf2238a9c646498b00ffb1` with an isolated PostgreSQL database. 2. Create a synthetic internal user with `tpm_limit=120000` and `rpm_limit=…