feat(SDK-1191): add unstable hook-backed payroll history

[krisxcrash]

Summary

Add a hook-backed PayrollHistory implementation behind the payrollHistoryHooks unstable feature flag. The flag defaults to off, preserving the existing component behavior while the migration is reviewed.

Changes

• Extract historical payroll fetching, filters, pagination, and cancellation into internal usePayrollHistory, following the existing UNSTABLE_PayrollEditEmployee pattern.
• Return plain payroll API rows and wire requests; both implementations derive row values through the same presentation helper. Share and validate payroll identifiers before exposing row actions.
• Run the cancellation success callback inside submit error handling, so synchronous callback exceptions reach a React boundary and produce a failed submit metric.
• Preserve event payloads, dictionary overrides, custom loading/error components, and cached wire data after background refresh failures.
• Remove duplicate history/empty stories, rename the error story to QueryError, and remove the unused status.isFetching field.
• Add legacy/hook parity coverage and Storybook scenarios matching the original history stories, plus loading, query errors, cancellation errors, and pagination.

Error boundary behavior

Query behavior matches legacy: payroll query errors reach the component boundary, initial wire-query errors reach it, and cached wire refresh errors remain invisible in the component. Headless consumers receive query errors through errorHandling.

Unexpected cancellation callback errors follow each implementation's boundary placement: legacy handles them at its outer boundary; the hooks implementation handles them at its component boundary and emits ERROR with the raw exception. Both record a failed submit metric. Regression coverage asserts this distinction explicitly.

Related

• SDK-1191
• Implementation pattern: feat: move overtime workweek info alert into UNSTABLE_PayrollEditEmployee #2757

Testing

• 159 targeted tests pass, including 72 legacy/hook component and behavior cases. Coverage includes callback exceptions, missing payroll IDs, initial query retry, and cached wire refresh failures.
• TypeScript, production build, formatting, ESLint, and documentation build pass. ESLint reports existing warnings.
• Previous full-suite run: 4,302 passed, one expected failure, and one failure in the unchanged contractor CreatePayment tests. That file's 19 tests passed on isolated rerun.
• Manually verified the hooks stories in Storybook: all 11 status examples, successful cancellation, empty/loading/query-error states, cancellation errors, pagination, and date filtering/reset.

To review, run npm run storybook and open Domain / Payroll / UNSTABLE_PayrollHistory. Compare PayrollHistoryStory, AllStatusesShowcase, CancelDialog, EmptyState, and WithDateFilter with the original stories. To exercise the public component's hook path, set unstableFeatures={{ payrollHistoryHooks: true }} on GustoProvider.

[serikjensen]

Put a parking lot item on the schedule to discuss hooks direction! mentioned that i'm hesitant to roll these out given we are entering the partner stabilization phase