fix(deps): bump user-reaching deps for security advisories

[ehe9991]

Problem

Several uv.lock pins with critical/high advisories reach users:

• anyio 4.13.0 (GHSA-82r6-8w77-94w6, critical) and idna 3.13 (GHSA-65pc-fj4g-8rjx) ship inside the standalone parallel-cli binary. release.yml builds it from uv sync --extra cli, so lock pins become the bundled versions.
• snowflake-connector-python 4.4.0 (GHSA-5cc2-282f-jjq2, critical: TLS hostname not verified; GHSA-qqj6-54q6-cxv6: credentials written to logs) sits on enrich deploy --system snowflake, which sends the user's Snowflake password. Its transitive pyjwt, urllib3 and cryptography add further highs.
• cryptography, pyasn1, urllib3 and idna in the bigquery extra carry highs.

Solution

• Lock bumps: anyio 4.15.1, idna 3.20, snowflake-connector-python 4.7.5, pyjwt 2.15.1, cryptography 50.0.2, urllib3 2.8.0, pyasn1 0.6.4, plus required transitive bumps pyopenssl 26.4.0 and typing-extensions 4.16.0.
• Set the snowflake extra to >=4.7.3,<5. Without the floor, pip keeps an already-installed vulnerable connector. 4.7.1 fixes the TLS bug, and 4.7.3 also fixes the logging bug (3.x never got it).
• The <5 cap: connector 5.0.0 (2026-10-15) needs Python 3.11+, drops most of its dependencies, and has no published changelog. Without the cap, the new floor upgrades existing 3.11+ installs straight onto it. Fresh resolution with the cap gives 4.8.0 on Python 3.10–3.13.
• Supply chain: every target version was published at least 7 days ago. Each has the same PyPI owners and the same PEP 740 provenance publisher as the current pin, or neither version has provenance. All 104 changed artifact hashes match PyPI's digests. OSV reports no advisories on any target.
• Other extras' transitive pins stay at the user's resolver; this PR only raises the floor where our code sends credentials.
• The lock holds snowflake at 4.7.5. 4.8.0 turns OCSP revocation checks off unless ocsp_fail_open is set, which _build_connection_params does not do. pip users who resolve 4.8+ get that default either way. Whether to pass ocsp_fail_open=True is a separate decision.
• cryptography 49+ ships no macOS x86_64 or universal2 wheels. Intel-Mac contributors running uv sync --all-extras build it from source, which needs Rust. The release binary does not include cryptography.

Users get the binary fixes on the next release (binaries, npm parallel-web-cli, Homebrew cask). pip users get the new floor on the next PyPI release.

Dev-only tooling bumps (GitPython, tornado, virtualenv, setuptools, datamodel-code-generator) are in a separate PR.

Testing

• CI green: tests on 3.10–3.14, lint, cli-test. Locally: uv lock --check, 846 pytest passed, ruff, tach, ty, and every parallel-cli … --help.
• osv-scanner on uv.lock: only the dev tools covered by chore(deps): bump vulnerable dev-only tooling #160 remain. With fix(deps): bump user-reaching deps for security advisories #159 and chore(deps): bump vulnerable dev-only tooling #160 merged locally: no issues. This PR, chore(deps): bump vulnerable dev-only tooling #160 and build: keep dev-only packages out of the standalone binary #161 merge together cleanly.
• Local darwin-arm64 binary build runs and bundles anyio 4.15.1 and idna 3.20.
• A fresh pip install of .[snowflake] resolves connector 4.8.0, and every key _build_connection_params passes is still a connector config key.
• ⚠️ Snowflake deploy against a live account is not exercised. The connector moves 4.4 → 4.7.5 (same major).

Supersedes Dependabot #102, #109, #127, #133, #138.

🤖 Generated with Claude Code