codegen: simplify pagination detection to match actual API

Only check for "next_token" (response) and "token" (query param) —
the actual field names used by all HeyGen v3 endpoints. Removed
speculative support for "cursor" and "page_token" that don't exist.

Updated test_spec.yaml to use "next_token" (was "token").

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: somanshreddy

codegen/grouper.go

@@ -458,13 +458,8 @@ func detectPagination(op *openapi3.Operation, pathItem *openapi3.PathItem) bool
 		schemasToCheck = append(schemasToCheck, dataProp.Value)
 	}
 	for _, schema := range schemasToCheck {
-		for _, candidate := range []string{"next_token", "token", "cursor"} {
-			if _, ok := schema.Properties[candidate]; ok {
-				hasCursorField = true
-				break
-			}
-		}
-		if hasCursorField {
+		if _, ok := schema.Properties["next_token"]; ok {
+			hasCursorField = true
 			break
 		}
 	}
@@ -482,8 +477,7 @@ func detectCursorParam(pathItem *openapi3.PathItem, op *openapi3.Operation) stri
 		if param == nil || param.In != "query" {
 			continue
 		}
-		switch param.Name {
-		case "token", "cursor", "page_token":
+		if param.Name == "token" {
 			return param.Name
 		}
 	}

codegen/testdata/test_spec.yaml

@@ -37,7 +37,7 @@ paths:
                         type: array
                         items:
                           type: object
-                      token:
+                      next_token:
                         type: string
     post:
       tags: [Videos]