Add NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY to Vercel <> Supabase Integration

# Bug report <!-- ⚠️ We receive a lot of bug reports which have already been solved or discussed. If you are looking for help, please try these first: - Docs: https://docs.supabase.com - Discussions: https://github.com/supabase/supabase/discussions - Discord: https://discord.supabase.com Before opening a bug report, please verify the following: --> - [ x] I confirm this is a bug with Supabase, not with my own application. - [x ] I confirm I have searched the [Docs](https://docs.supabase.com), GitHub [Discussions](https://github.com/supabase/supabase/discussions), and [Discord](https://discord.supabase.com). ## Describe the bug The Supabase / Vercel Integration does not include NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY for accounts that have migrated to using the asymmetric JWTs. ## To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Fire up a new Supabase project using the useClaims() method 2. Deploy the project in Vercel 3. Go to Vercel Settings, Click integrations, search supabase, link supabase account/Project 4. See Missing NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY in Vercel env vars ## Expected behavior Expected to see NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY as a variable in my environment variables after I integrate ## Screenshots N/A ## Additional context N/A