Use getClaims in the middleware for faster requests (#305)

* chore(version): bump version to 2.12.1 and update auth middleware to use getClaims instead of getUser

- Incremented version in package.json from 2.12.0 to 2.12.1.
- Refactored middleware to replace supabase.auth.getUser() with supabase.auth.getClaims() for improved claims handling.
- Updated user checks in middleware to validate claims instead of user object.

* refactor(middleware): update user authentication to utilize getClaims for improved claims validation

- Replaced calls to supabase.auth.getUser() with supabase.auth.getClaims() in middleware for better claims handling.
- Adjusted user validation checks to ensure claims are used instead of the user object, enhancing security and consistency in authentication flow.

* refactor(auth): update VerifyPage to use getClaims for user validation

- Replaced the use of supabase.auth.getUser() with supabase.auth.getClaims() in the VerifyPage component for improved claims handling.
- Adjusted user validation logic to check for claims instead of the user object, enhancing security and consistency in the authentication flow.

apps/web/app/auth/verify/page.tsx

@@ -25,11 +25,9 @@ export const generateMetadata = async () => {
 async function VerifyPage(props: Props) {
   const client = getSupabaseServerClient();
 
-  const {
-    data: { user },
-  } = await client.auth.getUser();
+  const { data } = await client.auth.getClaims();
 
-  if (!user) {
+  if (!data?.claims) {
     redirect(pathsConfig.auth.signIn);
   }
 
@@ -44,7 +42,7 @@ async function VerifyPage(props: Props) {
 
   return (
     <MultiFactorChallengeContainer
-      userId={user.id}
+      userId={data.claims.sub}
       paths={{
         redirectPath,
       }}