GraphQl: Fix limit of nested edge field applied only to first parent

[BigRoy]

Bug

A limit set on a nested edge field (e.g. at most 1 link per version) is applied only to the first parent item. All following parents get no nested items.

On a local server with links limited to 1 for 5 versions (four of them have 793 links):

• develop: [1, 0, 0, 0, 0]
• this PR: [1, 1, 1, 1, 1]

Cause

The nested field keeps _fetched_counter, but it was never reset when the parent moved to its next item (reset_cursor resets only cursor and need_query). After the first parent reached the limit, get_filters computed limit - fetched = 0 (or negative) and sent first: 0 for all other parents.

Fix

• Reset _fetched_counter in reset_cursor, so the limit is counted per parent item.
• Never send a page size lower than 1; stopping is already handled by need_query once the limit is reached.

Reproduce

import ayon_api
from ayon_api.graphql_queries import versions_graphql_query

con = ayon_api.get_server_api_connection()
project_name = "<project with version links>"
version_ids = [v["id"] for v in con.get_versions(project_name, fields={"id"})][:5]

query = versions_graphql_query({"id", "links.id"})
query.set_variable_value("projectName", project_name)
query.set_variable_value("versionIds", version_ids)
query.get_field_by_path("project/versions/links").set_limit(1)
print([len(v["links"]) for v in query.query(con)["project"]["versions"]])

Compare with len(con.get_version_links(project_name, version_id)) for the same versions to make sure they do have links.

Testing notes

• tests/test_graphql_nested_limit.py reproduces it with an in-memory fake server and also checks no first: 0 is sent.

🤖 Generated with Claude Code