chore(client): correct token location check in parseRequestToken

Fixed a typo in the `parseRequestToken` function to ensure the correct handling of token placement in the request headers. The condition mistakenly checked for 'headers' instead of 'header', which could lead to incorrect or failed token handling in API requests. This fix aligns with the standard naming convention and ensures the function behaves as intended.

packages/client/utils/parseRequestToken.ts

@@ -39,7 +39,7 @@ export function parseRequestToken(context: Partial<RequestContext>, options: Fet
   }
 
   // --- Append the token to the path parameters.
-  else if (tokenLocation === 'headers') {
+  else if (tokenLocation === 'header') {
     context.init = context.init ?? {}
     context.init.headers = context.init.headers ?? {}
     if (tokenProperty) setHeader(context.init.headers, tokenProperty, token)