fix: normalize bare-array list responses into { Data, TotalRecords }

[asachs01]

Summary

The live ConnectWise Automate REST API returns list endpoints (/Computers, /Clients, /Locations, /Alerts, /Contacts, /Groups, /Groups/:id/Members, /Patches, /Patches/ComputerPatches, /Scripts) as a bare JSON array, but this library's types model them as { Data, TotalRecords }. HttpClient.handleResponse does an unchecked response.json() as T cast, so the mismatch compiled cleanly and only surfaced at runtime — any consumer reading response.Data got undefined (Cannot read properties of undefined (reading 'length'), etc).

This was already hit downstream in connectwise-automate-mcp (#35), which now compensates by normalizing both shapes at its own boundary (src/utils/results.ts) — this PR fixes it at the source so every other consumer doesn't have to re-implement the same shim.

Changes

• New normalizeListResponse<T>() helper in src/types/common.ts: accepts either a bare T[] or the documented { Data, TotalRecords } envelope and always returns the envelope shape.
• Applied it in every resource method that hits a list-shaped endpoint: alerts.list, clients.list, clients (Locations) .list, computers.list, contacts.list, groups.list, groups.members, patches.list, patches.computerPatches, scripts.list.
• Applied the same fix to PaginatedIterable in pagination.ts (backs every resource's listAll()), which had the identical response.Data assumption called out in the issue.

Test plan

• npm run typecheck — clean
• npm test — 95/95 pass (added 4: a unit suite for normalizeListResponse covering bare-array, empty-array, and pass-through-envelope cases, plus an integration test asserting computers.list() correctly unwraps a mocked bare-array /Computers response)
• npm run build — clean
• npm run lint — 0 errors/warnings

Fixes #38

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}