Missing features for using management API in CI

CI/CD workflows is mentioned as one of the main use cases for the management api, but it seems like there are a few critical missing features? For context, our use case is to spin up a supabase project, apply migrations, run browser tests against the project, and spin down the supabase project. We want to do this instead of just testing against a local Supabase instance because the environment between the two often diverge. For example, currently, 1) we [can't use realtime locally]( 2) permissions are often different on cloud instances vs local instances even with the same migration scripts because supabase db reset runs as a superuser, where as supabase db push runs as postgres. Also, if there is a new migration involved, we don't want to apply that to staging for a test triggered by a PR, since that would pollute the staging server for other PR tests. The missing features: 1. There is no way to delete a supabase project programmatically. 2. The 2 project free tier lim…