GraphQl: Fix limit stopping early with nested pagination

[BigRoy]

Bug

When an edge field has a limit (set_limit) and it also has a nested edge field (e.g. links), fewer items than the limit are returned whenever a nested field needs more than one page.

Example: versions limited to 3, each with 700 links → only 1 version is returned.

Cause

Nested edge fields can't be paged for multiple parents at once, so the parent item is queried again (same cursor) until its nested field is fully fetched. _fetched_counter += len(edges) ran on each of those re-queries, so the same parent was counted once per nested page (700 links = 3 pages = counted 3 times) and the limit was reached after the first parent.

Fix

Count only items that were newly added to the output (len(node_values) before/after parsing the page). Re-parsed items are already merged by cursor, so they don't increase the count.

Reproduce

No public helper currently sets a limit together with nested edge fields, so this is reproduced with a custom query. Requires a project where the first versions have more than 300 links:

import ayon_api
from ayon_api.graphql_queries import versions_graphql_query

con = ayon_api.get_server_api_connection()
query = versions_graphql_query({"id", "links.id"})
query.set_variable_value("projectName", "<project>")
query.get_field_by_path("project/versions").set_limit(3)
versions = query.query(con)["project"]["versions"]
print(len(versions), [len(v["links"]) for v in versions])
# develop: 1 [793]
# this PR: 3 [793, 793, 793]

Testing notes

• tests/test_graphql_limit_nested_pagination.py reproduces it with an in-memory fake server (5 versions × 700 links, limit 3).
• Without limits nothing changes: get_versions_links returns the same data as before.

🤖 Generated with Claude Code