fix(tickets): page_size ignored on first page, dateoccurred_start/end silently ignored

[asachs01]

Summary

Two ticket-listing bugs reported by a community user running halopsa-mcp v1.7.9:

• page_size ignored on the first page. HaloPSA only honors page_size when page_no is also present on the same request — page_size alone is accepted but silently ignored, falling back to HaloPSA's own default (50) for that implicit first page. addPageinate() (shared by every resource) now defaults page_no to 1 whenever page_size is set without it, matching what PaginatedIterable (.listAll()) already did correctly on every page. This also explains the reported record_count inconsistency — it only reports the true total once pagination is genuinely active on every request.
• dateoccurred_start/dateoccurred_end silently ignored. Neither is a real HaloPSA query parameter — confirmed directly against the live /api/swagger/v2/swagger.json spec. The actual mechanism is datesearch=dateoccured (HaloPSA's own misspelling) + startdate/enddate. TicketsResource.list()/.listAll() now translate the pair before the request goes out.

Verified

• npm run typecheck / npm run lint / npm run build: clean
• npm test: 264/264 passing
• New integration tests assert the actual outgoing query string via MSW request interception (not just the response), so a regression here would fail loudly rather than silently

Note for a follow-up (not fixed here)

While tracing this, I found AppointmentListParams (src/types/appointments.ts) has the identically-shaped startdate_start/startdate_end synthetic filter pair, and AppointmentsResource.buildListParams still passes them through untranslated — the same latent bug, just not the one reported. Leaving that out of scope for this PR since it wasn't reported and I don't want to bundle an unverified fix; flagging here in case it's worth its own issue.

Test plan

• Unit tests for addPageinate()'s new page_no default (both the "defaults to 1" and "doesn't override an explicit page_no" cases)
• Integration tests asserting the real outgoing page_no/page_size/pageinate query params on a single-page .list() call
• Integration tests asserting dateoccurred_start/dateoccurred_end translate to datesearch/startdate/enddate and don't leak through verbatim

---

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