perf(graphql): use depth 0 in auth/apiKey for graphQL requests (#13895)

### What?
Sets depth to 0 when finding the corresponding user in auth/apiKey.
This matches the current behavior of auth/jwt

### Why?
Optimizes the authentication step by making just one database query
instead of two, when using sessions. Particularly impactful when there's
latency between Payload and the database

### How?
By leveraging the already existing isGraphQL flag of the
AuthStrategyFunction

Co-authored-by: Ricardo Tavares <rtavares@cloudflare.com>
Co-authored-by: Dan Ribbens <dan.ribbens@gmail.com>

Author: 3 people

packages/payload/src/auth/strategies/apiKey.ts

@@ -7,7 +7,7 @@ import type { AuthStrategyFunction } from '../index.js'
 
 export const APIKeyAuthentication =
   (collectionConfig: SanitizedCollectionConfig): AuthStrategyFunction =>
-  async ({ headers, payload }) => {
+  async ({ headers, isGraphQL = false, payload }) => {
     const authHeader = headers.get('Authorization')
 
     if (authHeader?.startsWith(`${collectionConfig.slug} API-Key `)) {
@@ -53,7 +53,7 @@ export const APIKeyAuthentication =
 
         const userQuery = await payload.find({
           collection: collectionConfig.slug,
-          depth: collectionConfig.auth.depth,
+          depth: isGraphQL ? 0 : collectionConfig.auth.depth,
           limit: 1,
           overrideAccess: true,
           pagination: false,