## Description

Several DashScope Qwen models are missing pricing data in `model_prices_and_context_window.json`, causing `$0` cost tracking when routed via the `dashscope/*` wildcard.

## Affected models

| Model | Status in pricing table | Actual pricing (from [DashScope](https://help.aliyun.com/zh/model-studio/model-pricing)) | Constraints| |-------|------------------------|----------------------------------------------|----------| | `dashscope/qwen3.7-max` | Missing entirely | ¥12.00/M input, ¥36.00/M output || | `dashscope/qwen3.7-plus` | Missing entirely | ¥2.00/M input, ¥8.00/M output |0<Token≤256K| | `dashscope/qwen3.7-plus` | Missing entirely | ¥2.00/M input, ¥8.00/M output |256K<Token≤1M| | `dashscope/qwen3.6-plus` | Missing entirely | ¥2.00/M input, ¥12.00/M output |0<Token≤256K| | `dashscope/qwen3.6-plus` | Missing entirely | ¥8.00/M input, ¥48.00/M output |256K<Token≤1M|

## Expected behavior

These models should have valid `input_cost_per_token` and `output_cost_per_token` entries so that spend tracking returns accurate cost data.

## Current behavior

Requests are routed correctly via the `dashscope/*` wildcard and tokens are tracked, but all cost values return `$0` …