chore(deps): update cryptography requirement from <50.0.0,>=46.0.3 to >=46.0.3,<51.0.0

docker/runners/runner-image.lock.json

@@ -1,12 +1,12 @@
 {
   "base_image_digest": "sha256:3ba65aa20f86a0fad9df2b2c259c613df006b2e6d0bfcc8a146afb8c525a9751",
   "gh_version": "2.67.0",
-  "identity_digest": "9091516a079d6979809d0b55150f4eff",
+  "identity_digest": "e2eeb76f4c47425cd66fff3df853fc01",
   "image_version": 6,
   "kubectl_version": "1.32.1",
   "python_version": "3.12",
   "runner_version": "2.334.0",
-  "shared_env_digest": "df9727fff071d6f42d35f45f",
+  "shared_env_digest": "21fe88ae09228cc7499d770a",
   "shared_env_install_args": "--frozen --all-extras --all-groups --no-install-project",
   "uv_version": "0.6.14"
 }

pyproject.toml

@@ -92,13 +92,13 @@ dependencies = [
     # docker/Dockerfile.runtime force-installs cryptography>=50.0.0 after the
     # plugin installs. Raising the declared ceiling HERE is blocked on a
     # published omnibase-core release: omnibase-core==0.46.8 on PyPI declares
-    # cryptography>=46.0.3,<50.0.0, and `uv lock` fails closed --
-    #   Because omnibase-core>=0.46.8 depends on cryptography>=46.0.3,<50.0.0
+    # cryptography>=46.0.3,<51.0.0, and `uv lock` fails closed --
+    #   Because omnibase-core>=0.46.8 depends on cryptography>=46.0.3,<51.0.0
     #   and your project depends on cryptography>=50.0.0,<51.0.0 [...]
     #   your project's requirements are unsatisfiable.
     # The core-side raise is omnibase_core PR (OMN-15688); this line moves to
     # >=50.0.0,<51.0.0 in the same commit that bumps omnibase-core off 0.46.8.
-    "cryptography>=46.0.3,<50.0.0",
+    "cryptography>=46.0.3,<51.0.0",
     "sigstore>=4.0.0,<5.0.0",
     # packaging: PEP 440 version parsing/comparison for the release-identity
     # fitness node (node_release_identity_compute, OMN-14471). Previously a