fix(security): refresh Python dependency graphs

[0xjohnnydev]

Problem

The current Dependabot inventory maps 112 open alerts to CUA's Python dependency graphs. This is the Python-only part of #2719 so it can be reviewed and landed without the unrelated JavaScript lockfiles.

There are no application-source changes in this PR.

What changed

• Updated the root, CUA Bench, CUA CLI, sandbox-apps, and sandbox locks for patched GitPython, Pillow, aiohttp, cryptography, h2, pyasn1, PyMdown Extensions, setuptools, Click, and jaraco-context releases.
• Updated Torch to 2.13.0 and TorchVision to 0.28.0. Torch 2.12.1 requires setuptools below the patched 83.0.0 floor, so those updates need to land together.
• Kept the related Python locks in one PR because the same security floors repeat across them.

Definition of Done

• Represent all 112 currently open Python Dependabot alerts. Every affected Python manifest or lockfile is included and resolves outside the published vulnerable ranges.
• Keep each Python graph internally consistent. The root, CUA Bench, CUA CLI, sandbox-apps, and sandbox locks pass independent lock checks.
• Leave no known advisory in the audited exports. The exported root, CUA Bench, and CUA CLI graphs return no known vulnerabilities from pip-audit.
• Build the packages most affected by the resolution changes. SOM, CUA Bench, and CUA CLI build from the split branch.
• A maintainer reviews the Torch/TorchVision compatibility change. The upgrade is required to coexist with the patched setuptools floor, but it is larger than the other patch updates.
• Current-head GitHub Actions pass. All repository Actions triggered by this split pass.
• GitHub confirms alert closure after merge to main. A draft PR cannot prove final Dependabot closure.

Split provenance

This contains the Python files from #2719, unchanged, rebuilt on current main.

[github-actions]

📦 Publishable packages changed

This comment is status-only. Editing it or adding task-list checkboxes cannot authorize a release.
Only owner-applied release:<service> labels can do that.

• ⏸️ pypi/bench — no owner-authorized release label
• ⏸️ pypi/cli — no owner-authorized release label
• ⏸️ pypi/som — no owner-authorized release label

Ask the release owner to apply release:<service> labels to auto-release on merge (+ optional bump:minor or bump:major, default is patch).
Or add no-release to skip.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!