refactor(useCompaniesQueries): optimize cache update logic for category publishing

- Removed the invalidateQueries call to prevent unnecessary refetching and duplicate animations during category updates.
- Added a comment to clarify the rationale behind the change, ensuring better understanding of the cache synchronization process.

src/hooks/queries/useCompaniesQueries.ts

@@ -227,10 +227,9 @@ export const useToggleCompanyCategoryPublished = () => {
       if (toastMessage) {
         toast.success(toastMessage);
       }
+      // Sync cache only — avoid invalidateQueries here: it refetches and produces a
+      // second `data` reference, which retriggers table row GSAP animations twice.
       updateOptimisticCategories(categoryId);
-      queryClient.invalidateQueries({
-        queryKey: [API_ENDPOINTS.COMPANIES.CATEGORIES.READ_ALL],
-      });
     },
   });
 };