Build(deps): Bump python-multipart from 0.0.26 to 0.0.32 in /python

[dependabot]

Motivation and Context

Bumps python-multipart from 0.0.26 to 0.0.32 to address multiple security advisories. The previous bump to 0.0.27 only covered the older <0.0.27 alert; version 0.0.32 (satisfying >=0.0.31) covers the newer python-multipart vulnerability alerts as well.

Description

• Adds python-multipart>=0.0.31 to override-dependencies in python/pyproject.toml. constraint-dependencies was insufficient because litellm[proxy] pins python-multipart exactly at ==0.0.27; an override is required to bypass that exact pin.
• Regenerated python/uv.lock — the resolver selected 0.0.32 (latest version satisfying >=0.0.31).

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines
• All unit tests pass, and I have added new tests where possible
• Is this a breaking change? If yes, add "[BREAKING]" prefix to the title of the PR.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[moonbox3]

@copilot: update this PR to bump python-multipart to 0.0.31 instead of 0.0.27 and regenerate python/uv.lock. If the resolver will not choose 0.0.31 from existing constraints, add a security floor in python/pyproject.toml under [tool.uv] constraint-dependencies for python-multipart>=0.0.31, then regenerate python/uv.lock. The current bump only fixes the old <0.0.27 alert; 0.0.31 should cover the newer python-multipart alerts too.

[Copilot]

@copilot: update this PR to bump python-multipart to 0.0.31 instead of 0.0.27 and regenerate python/uv.lock. If the resolver will not choose 0.0.31 from existing constraints, add a security floor in p...

Done. constraint-dependencies couldn't work here because litellm[proxy] pins python-multipart exactly at ==0.0.27, so the constraint floor was silently ignored. I added python-multipart>=0.0.31 to override-dependencies instead (alongside the existing mcp[ws], uvicorn, and opentelemetry-semantic-conventions overrides), then regenerated python/uv.lock. The resolver picked 0.0.32 (the latest satisfying >=0.0.31) — see commit Build(deps): Bump python-multipart to 0.0.32 via override-dependencies floor >=0.0.31.