### Check for existing issues

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

### The Feature

I would like LiteLLM to support provider quota pools, also called provider packages, as a first-class routing concept.

Today LiteLLM Router supports multiple deployments, fallback, load balancing, budgets, and rate limits. However, enterprise deployments often purchase quota from multiple vendors or accounts, and each quota package may have its own usage window and remaining capacity.

Desired provider package fields could include:

- `logical_model` - `provider` - `package_name` - `provider_model_name` - `provider_api_key_ref` - `provider_priority` - `routing_weight` - `max_5h_calls` - `max_daily_calls` - `max_weekly_calls` - `max_monthly_calls` - `used_5h_calls` - `used_daily_calls` - `used_weekly_calls` - `used_monthly_calls` - `cache_ttl_seconds` - `is_active` - `metadata.capabilities` - `metadata.max_context_tokens` - `metadata.stability_score`

Desired behavior:

1. Admins define quota pools/packages for each logical model. 2. Router selects a provider package based on remaining quota, priority, routing weight, and capabilities. 3. LiteLLM …