Ignore secrets that start with SUPABASE_ instead of throwing error

[bombillazo]

Describe the bug

It is disruptive to the secrets setting process to have to filter variables that start with SUPABASE_ (which are used to locally test) because the cli will throw errors when trying to push the .env file to the secrets in remote.

To Reproduce Steps to reproduce the behavior:

1. Have a .env file used to run local edge functions with a secret starting with SUPABASE_
2. Run supabase secrets set --env-file .env
3. An error is thrown, effectively blocking setting all other variables in the .env

Expected behavior

The variables starting with SUPABASE_ are simply ignored and the rest are uploaded as expected

• Version of CLI [e.g. v1.131.1]