fix: bump cryptography to ~=50.0

[gjtorikian]

Summary

• Bump the cryptography requirement from ~=49.0 to ~=50.0 (>=50.0,<51.0) and re-lock to 50.0.0.
• Clears CVE-2026-69247 / GHSA-g6cj-pr64-35w5 (PKCS#7 EnvelopedData decryption exposes a Bleichenbacher oracle), which affects >=44.0.0,<50.0.0 and is fixed in 50.0.0.
• The SDK only uses long-stable cryptography APIs (Fernet in session.py, Cipher/algorithms/modes + default_backend in vault/_resource.py), which are unchanged in the 50.x line.

Closes #705

[greptile-apps]

Greptile Summary

Updates the supported cryptography release line from 49.x to 50.x to consume the security fix in 50.0.0.

• Raises the direct dependency constraint to cryptography~=50.0.
• Regenerates the lockfile with cryptography 50.0.0 artifacts and matching package metadata.

Confidence Score: 5/5

The PR appears safe to merge with no actionable changed-code defects identified.

The manifest and lockfile consistently select cryptography 50.0.0, while the other advisory-matched dependencies are unchanged from the base branch and do not represent regressions introduced here.

Important Files Changed

Filename	Overview
pyproject.toml	Updates the direct cryptography requirement from the 49.x release line to 50.x; no actionable compatibility defect was identified.
uv.lock	Consistently re-locks cryptography at 50.0.0 and updates its artifact hashes and project dependency metadata.

_{Reviews (1): Last reviewed commit: "chore: bump cryptography to ~=50.0" | Re-trigger Greptile}