fix: paginate getProjects/getClients so all results resolve

[janis-ps]

Problem

getProjects and getClients issue a single un-paginated GET to the Toggl v9 list endpoints. Those endpoints paginate by page/per_page (sorted by name) and return only the first page by default, silently dropping the rest.

As a result, any project or client past the first page fails name resolution and surfaces as the Project <id> fallback in reports and summaries. Workspaces with more projects than a single page hit this for everything after the first page.

Fix

• Add a private requestAllPages() helper that walks ?per_page=200&page=N until a short page is returned.
• Two safety guards: a non-advancing-page detector (breaks if an endpoint ignores page and re-returns the same window, preventing an infinite loop) and a MAX_PAGES backstop.
• Route both getProjects and getClients through it (clients had the identical bug).

This is offset pagination (page/per_page), verified against the v9 /workspaces/{id}/projects endpoint — page=2 returns a distinct, later, name-sorted window.

Tests

TDD: three tests written first and watched fail, then pass:

• fetches every page until a short page (multi-page),
• single request when the first page is short,
• stops instead of looping when the endpoint ignores page.

Full suite green (30 passed, 3 pre-existing skips), tsc --noEmit clean, ESLint 0 errors.

Notes / out of scope

• Pagination only. getProjects still uses Toggl's default active-only filter, so genuinely archived projects still won't name-resolve — left for a separate change (e.g. an active=both option).
• PAGE_SIZE is hardcoded to 200 rather than wired to the documented TOGGL_BATCH_SIZE env var, since the TogglAPI constructor doesn't currently receive config. Happy to thread it through if preferred.

[jack-arturo]

I reviewed the diff and ran the verification set locally after checking out the branch:

• npm run build
• npm test (33/33 passing)
• npm run lint (0 errors; existing warnings remain)
• npm audit --audit-level=high (0 high/critical; existing moderate brace-expansion advisory only)

I also approved the pending fork CI/Security runs; GitHub checks are now passing. The pagination helper is scoped to projects/clients and has focused coverage for multi-page, short-page, and non-advancing-page behavior.