fix(iam): return paginationToken from listPolicies (#206)

The AWS-standard ListPolicies response nests IsTruncated and Marker
inside ListPoliciesResult, but they were read from the top level, so the
next-page token was always undefined — callers could never page past the
first result set. Read them from ListPoliciesResult, gated on IsTruncated,
matching the existing listPoliciesForAccessKey handling.

Assisted-by: Claude Opus 4.8 via Claude Code

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: designcode

.changeset/iam-list-policies-pagination-token.md

@@ -0,0 +1,5 @@
+---
+"@tigrisdata/iam": patch
+---
+
+Fix `listPolicies` never returning a `paginationToken`. The `IsTruncated` and `Marker` fields are nested inside `ListPoliciesResult` in the API response, but were being read from the top level, so the next-page token was always `undefined`.

packages/iam/src/lib/policy/list.ts

@@ -15,9 +15,9 @@ export type ListPoliciesResponse = {
 };
 
 type ListPoliciesApiResponse = {
-  IsTruncated: boolean;
-  Marker?: string;
   ListPoliciesResult: {
+    IsTruncated: boolean;
+    Marker?: string;
     Policies: Array<{
       Arn: string;
       AttachmentCount: number;
@@ -75,8 +75,9 @@ export async function listPolicies(
 
   return {
     data: {
-      paginationToken:
-        response.data.Marker !== '' ? response.data.Marker : undefined,
+      paginationToken: response.data.ListPoliciesResult?.IsTruncated
+        ? response.data.ListPoliciesResult.Marker || undefined
+        : undefined,
       policies:
         response.data.ListPoliciesResult?.Policies?.map((policy) => ({
           attachmentCount: policy.AttachmentCount,