fix: make mutations correctly invalidate queries

[ChibiBlasphem]

Simple PR to naively and manually invalidate queries to avoid stale data being kept in the app.

A further PR will add conventions on query caching strategy and a more streamlined way of invalidating related queries

---

Note

Standardizes React Query keys to cases and adds onSuccess invalidation to refresh cases data after mutations.

• Queries/Cases (React Query):
  • Standardize query keys from ['case', ...] to ['cases', ...] across mutations and useCreateKycEnrichmentQuery.
  • Add useQueryClient and onSuccess handlers to invalidate ['cases'] after mutations in:
    • useAddCommentMutation, useAddRuleSnoozeMutation, useAddToCaseMutation, useCloseCaseMutation, useCreateCaseMutation, useEditAssigneeMutation, useEditInboxMutation, useEditNameMutation, useEditSuspicionMutation, useEditTagsMutation, useEscalateCaseMutation, useMassUpdateCasesMutation, useOpenCaseMutation, useSnoozeCaseMutation.

^{Written by Cursor Bugbot for commit 6c81eca. This will update automatically on new commits. Configure here.}

[Pascal-Delange]

I don't have specific questions on the code directly, just a sanity check perhaps: did you make sure that it does not reset filters and pagination state when we do a batch action in the inbox ?

[ChibiBlasphem]

I don't have specific questions on the code directly, just a sanity check perhaps: did you make sure that it does not reset filters and pagination state when we do a batch action in the inbox ?

Filters and pagination states are parameters for a query. Query invalidations clear the cache stored for a query. So invalidating query cannot reset filters and pagination states, only the displayed results.

[Pascal-Delange]

cool!