Name the Supabase ENVs as Supabase itself does: SUPABASE_ANON_KEY and SUPABASE_SERVICE_ROLE_KEY

[MichaelSchmidle]

Is your feature request related to a problem? Please describe.

This is a request for a small "convenience" feature. I use Vercel to deploy my Nuxt 3 app with Supabase backend. Vercel and Supabase offer an integration which automatically populates Supabase environment variables in Vercel. However, the naming of these ENV do not match what's required with the Nuxt Supabase module:

• ENVs that Supabase syncs to Vercel: SUPABASE_ANON_KEY and SUPABASE_SERVICE_ROLE_KEY
• ENVs that the Supabase Nuxt Module uses: SUPABASE_KEY and SUPABASE_SERVICE_KEY

So, one has to manually sync those two ENVs in Vercel.

Describe the solution you'd like

Let's use the naming of the ENVs as Supabase itself does. This will enable the sync feature in Vercel (and possibly integrations with other Supabase partners).

I recognize that this would break existing installations, so the module would have to check for old and new namings (at least for a grace period before the old names become deprecated).

Thanks for considering that.

Describe alternatives you've considered

Manual sync.