Add missing roles field to getUserPermissions types

[dshoen619]

Summary

• Adds roles?: string[] to TenantPermissions and ResourcePermissions interfaces in src/enforcement/interfaces.ts
• The PDP returns a roles array in getUserPermissions responses, but the SDK types were missing this field, forcing users to use as any type assertions

Fixes PER-14323

[linear]

PER-14323 SDK TypeScript types missing roles field in getUserPermissions response

[Copilot]

Pull request overview

This PR updates the SDK’s getUserPermissions response typing to match what the PDP actually returns, removing the need for consumers to rely on as any when accessing roles.

Changes:

• Adds an optional roles?: string[] field to TenantPermissions.
• Adds an optional roles?: string[] field to ResourcePermissions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[zeevmoney]

Verified the roles?: string[] addition end-to-end against the source of truth:

• permit-backend rego emits {"permissions": [...], "roles": [...]} per entry in user_permissions.
• PDP (/user-permissions) struct: roles: Option<Vec<String>> with serde skip_serializing_if = "Option::is_none" → field name roles, omitted when absent (never null), string array when present.
• SDK passes the PDP response through untouched as IUserPermissions.

The type matches on field name, string[] ↔ Vec<String>, and optionality. Adding roles? to both TenantPermissions and ResourcePermissions is required for result[key].roles to type-check on the union; tsconfig has no noUncheckedIndexedAccess, so access works without as any. Well-isolated, correct.