feat(hooks): enhance useAggregateRecords to check access token pair before querying (#19845)

- Added a new dependency on `useHasAccessTokenPair` to ensure that the access token pair is validated before executing the aggregate query.
- Updated the query skip condition to include a check for the access token pair, enhancing security and ensuring proper permissions are enforced.

This change improves the overall integrity of the data fetching process in the `useAggregateRecords` hook.

packages/twenty-front/src/modules/object-record/hooks/useAggregateRecords.ts

@@ -1,5 +1,6 @@
 import { useQuery } from '@apollo/client/react';
 
+import { useHasAccessTokenPair } from '@/auth/hooks/useHasAccessTokenPair';
 import { useApolloCoreClient } from '@/object-metadata/hooks/useApolloCoreClient';
 import { useObjectMetadataItem } from '@/object-metadata/hooks/useObjectMetadataItem';
 import { type RecordGqlFieldsAggregate } from '@/object-record/graphql/types/RecordGqlFieldsAggregate';
@@ -45,10 +46,16 @@ export const useAggregateRecords = <T extends AggregateRecordsData>({
 
   const hasReadPermission = objectPermissions.canReadObjectRecords;
 
+  const hasAccessTokenPair = useHasAccessTokenPair();
+
   const { data, loading, error } = useQuery<RecordGqlOperationFindManyResult>(
     aggregateQuery,
     {
-      skip: skip || !isDefined(objectMetadataItem) || !hasReadPermission,
+      skip:
+        skip ||
+        !isDefined(objectMetadataItem) ||
+        !hasReadPermission ||
+        !hasAccessTokenPair,
       variables: {
         filter,
       },