`_supavisor` schema tables deleted when running `db reset`

[bombillazo]

Describe the bug

Running supabase db reset deletes the tables in the _supavisor schema, causing issues running the local stack.

To Reproduce Steps to reproduce the behavior:

1. Run supabase start
2. Run supabase db reset

After the reset, the _supavisor tables no longer exist.

Expected behavior Resetting db keeps all expected schemas. To fix the issue we need to stop/start the stack to restore the schema.

System information Rerun the failing command with --create-ticket flag.

• Version of CLI: 1.183.5
• Versions of services: supabase/postgres │ 15.1.1.73 │ 15.1.1.78 supabase/gotrue │ v2.154.2 │ v2.155.3 postgrest/postgrest │ v12.2.1 │ v12.2.2 supabase/realtime │ v2.29.15 │ - supabase/storage-api │ v1.6.8 │ v1.6.8 supabase/edge-runtime │ v1.54.10 │ - supabase/studio │ 20240701-05dfbec │ - supabase/postgres-meta │ v0.83.2 │ - supabase/logflare │ 1.4.0 │ - supabase/supavisor │ 1.1.56 │ - darthsim/imgproxy │ v3.8.0 │ -

Additional context If applicable, add any other context about the problem here.

• Version of Node.js v18.18.0

[bombillazo]

Any updates here? It's becoming pretty disruptive for our developers, especially our juniors.

[sweatybridge]

Thanks for the reminder. The fix will go into the stable release tomorrow.