## What happened

Per model rate limits (`model_rpm_limit` / `model_tpm_limit`) can be set on keys (key edit view) and on teams (`TeamInfo.tsx`, "Set per-model TPM/RPM limits that apply across the whole team"), but there is no UI to set them on internal users

The backend already accepts `model_rpm_limit` / `model_tpm_limit` on `NewUserRequest` and `UpdateUserRequest` (via `GenerateRequestBase`), so this is a missing UI surface for users

(For context, a broader report claimed per model limits work "only on keys, not users or teams". Teams do have it, so the real gap is users only.)

## Possible secondary bug on teams

In `TeamInfo.tsx` the save path sends `model_tpm_limit` / `model_rpm_limit` at the top level of the update payload, but the display path reads them back from `info.metadata?.model_tpm_limit` / `metadata?.model_rpm_limit`. If the backend does not mirror these into `metadata`, saved per model limits will not render back in the team view. Worth verifying end to end

## Repro

1. Virtual Keys -> edit key: has Model TPM/RPM Limit fields 2. Teams -> team info: has a per model TPM/RPM editor 3. Internal Users -> create/edit: no per model rate limit field

Confirmed against …