fix: use-next-public-supabase-anon-key

[i0dheerajdileep]

This PR addresses an issue where the SUPABASE_ANON_KEY environment variable was not correctly set as a public environment variable in the project. The key has now been updated to NEXT_PUBLIC_SUPABASE_ANON_KEY to ensure it is correctly exposed and accessible on the client side.

Changes Made:
Updated the environment variable from SUPABASE_ANON_KEY to NEXT_PUBLIC_SUPABASE_ANON_KEY.
Modified the relevant code to reflect this change, ensuring proper functionality without errors.

[vercel]

@i0dheerajdileep is attempting to deploy a commit to the snapcv Team on Vercel.

A member of the Team first needs to authorize it.

[jamaljm]

The key was declared to be SUPABASE_ANON_KEY so that it won't be exposed on the client side! Thanks for working on it, but it was intentionally proclaimed so that I could use the key specifically on the server side without exposing it on the client side.