Describe the bug
I'm not sure if this is a bug or a needed feature, but I would like to be able to load a different .env file name besides just .env. Apparently this is possible for local edge functions per Managing Secrets and Environment Variables, but not possible for the whole supabase? This doesn't make sense to me why it would only be available for local function testing and not the whole config.toml, so perhaps I am missing something?

To Reproduce
Steps to reproduce the behavior:
Run localhost with supabase start --env-file ./.env.development

Expected behavior
It would load the .env.development (or whatever name), instead of throwing an error:

unknown flag: --env-file

Desktop (please complete the following information):

• OS: Windows 11
• Version of CLI 1.99.5
• Version of Node.js 18

Thanks,

J