fix(cli): set limit on workflow list to avoid truncated results

[var-raphael]

Description

The hatchet trigger manual command fetches the list of workflows to display via WorkflowListWithResponse, but calls it with empty WorkflowListParams{}. This means no Limit is set, so the API falls back to its default page size — meaning tenants with more workflows than that default only ever see the first page, and can't select or trigger any workflow beyond it.

This fix sets an explicit Limit: 100 on both the interactive and non-interactive code paths, following the same pattern already used elsewhere in the CLI (e.g. crons.go, rate_limits.go, scheduled.go).

Fixes #4429

Type of change

• Bug fix (non-breaking change which fixes an issue)

What's Changed

• Added an explicit Limit: 100 to WorkflowListParams in both runManualInteractive and runManualNonInteractive in cmd/hatchet-cli/cli/trigger.go, so hatchet trigger manual can list and trigger workflows beyond the API's default page size.

Checklist

Changes have been:

• Tested (manually — verified go build ./cmd/hatchet-cli/... succeeds and golangci-lint reports no new issues in the affected package)
• Linted and formatted
• Documented (where applicable)
• Added to CHANGELOG (where applicable)

---

🤖 AI Disclosure

• I acknowledge that an LLM was used in the creation of this Pull Request, in accordance with Hatchet's AI_POLICY.md.

• Details: Claude was used to help investigate and diagnose the root cause of the bug (tracing from the issue report to the empty WorkflowListParams{} call), confirm the fix pattern by cross-referencing similar code elsewhere in the repo, and draft this PR description. All code changes were reviewed and applied by me.

[vercel]

@var-raphael is attempting to deploy a commit to the Hatchet Team on Vercel.

A member of the Team first needs to authorize it.