fix(ci): version-assignment scanned the WHOLE registry — livelocked releases

The "atomic free-version assignment" step paginated every container version
(`gh api --paginate .../versions`) to find the max release number. As the
registry accumulated tags this grew unbounded and hung the step for 30+ min,
livelocking every cloud release. Container versions are created newest-first and
version tags are monotonic, so the max is always on the newest page — query one
bounded page (?per_page=100) instead of the full history. Fast + correct.

.github/workflows/release.yml

@@ -434,11 +434,15 @@ jobs:
             git fetch --tags --force --quiet
             git_max="$(git tag -l 'v[0-9]*.[0-9]*.[0-9]*' \
               | sed 's/^v//' | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | sort -V | tail -1 || true)"
+            # Newest page only — NOT --paginate. Container versions are created
+            # newest-first and version tags are monotonic, so the highest version
+            # is always among the most-recent versions; paginating the WHOLE
+            # registry history is what livelocked this step as tags accumulated.
             cont_max=""
             if command -v gh >/dev/null 2>&1; then
-              cont_max="$(GH_TOKEN="$GH_PAT" gh api --paginate \
-                '/orgs/hanzoai/packages/container/cloud/versions' \
-                --jq '.[].metadata.container.tags[]' 2>/dev/null \
+              cont_max="$(GH_TOKEN="$GH_PAT" gh api \
+                '/orgs/hanzoai/packages/container/cloud/versions?per_page=100' \
+                --jq '.[].metadata.container.tags[]?' 2>/dev/null \
                 | sed 's/^v//' | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | sort -V | tail -1 || true)"
             fi
             max="$(printf '%s\n%s\n%s\n' "1.786.0" "$git_max" "$cont_max" \