`storage --local` command requires `SUPABASE_ACCESS_TOKEN`

[JakobKlotz]

Describe the bug
supabase storage --local requires a SUPABASE_ACCESS_TOKEN to be set/user logged in.

To Reproduce
Steps to reproduce the behavior:

supabase init
supabase start -x vector

Just like #3404, supabase vector fails on start up, hence it's excluded.

For example, the following command fails:

$ supabase storage ls --local --experimental --debug
Access token not provided. Supply an access token by running supabase login or setting the SUPABASE_ACCESS_TOKEN environment variable.

However, using a placeholder token works:

$ SUPABASE_ACCESS_TOKEN=sbp_0000000000000000000000000000000000000000 supabase storage ls --local --experimental
test/

Expected behavior
If I understood it correctly, the --local flag should work without any SUPABASE_ACCESS_TOKEN or user logged in.

System information

• Version of OS: Ubuntu 22.04.5 LTS

• Version of CLI: 2.20.12

• Version of Docker: 28.0.4, build b8034c0

• Versions of services:

  SERVICE IMAGE	LOCAL	LINKED
  supabase/postgres	15.8.1.060	-
  supabase/gotrue	v2.170.0	-
  postgrest/postgrest	v12.2.8	-
  supabase/realtime	v2.34.45	-
  supabase/storage-api	v1.19.3	-
  supabase/edge-runtime	v1.67.4	-
  supabase/studio	20250317-6955350	-
  supabase/postgres-meta	v0.88.2	-
  supabase/logflare	1.12.0	-
  supabase/supavisor	2.4.14	-