feat(workspace-users): exclude removed users by default

[scottlovegrove]

Summary

• getWorkspaceUsers now excludes users with removed: true by default; pass includeRemoved: true to include them.
• The Twist API endpoint /workspace_users/get (server: workspace_users.py get(id)) calls workspaces.get_users(ws.id) without the model's with_removed arg, so it's hardcoded to with_removed=True and exposes no override param. Filtering therefore happens client-side in the SDK — matching what twist-web (Redux selectors) and twist-cli already do.
• Applied to both execution paths: the awaited call filters in .then(); the batch path uses a new optional transform?: (data: unknown) => T hook on BatchRequestDescriptor, applied after schema parse in batch-builder.ts. The batch descriptor now also carries z.array(WorkspaceUserSchema), so batch results are validated too.

Prompted by twist-cli#245 review — the default belongs in the SDK so cli/MCP can drop their own filtering.

Test plan

• getWorkspaceUsers excludes removed users by default (awaited + batch)
• includeRemoved: true returns all users (awaited + batch)
• No include_removed/with_removed query param is sent (proves client-side filtering)
• Full suite green (245 tests), type-check, oxlint, oxfmt clean

🤖 Generated with Claude Code

[doistbot]

This PR cleanly introduces default client-side filtering for removed workspace users across both awaited and batch execution paths, nicely aligning the SDK's behavior with other clients. The implementation is straightforward and effectively addresses the current backend API limitations. A few refinements were noted around leveraging Zod's built-in transform capabilities to simplify the custom hook logic, optimizing performance by filtering out removed users before paying the schema validation cost, and strengthening the test suite through better mock reuse, consistent apiUrl helper usage, and explicit query parameter assertions on batch requests.

_{Share Feedback • Review Logs}