Schema drift with stripe/sync-engine

# Bug report <!-- ⚠️ We receive a lot of bug reports which have already been solved or discussed. If you are looking for help, please try these first: - Docs: https://docs.supabase.com - Discussions: https://github.com/supabase/supabase/discussions - Discord: https://discord.supabase.com Before opening a bug report, please verify the following: --> - [x] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the [Docs](https://docs.supabase.com), GitHub [Discussions](https://github.com/supabase/supabase/discussions), and [Discord](https://discord.supabase.com). ## Describe the bug Migrations diverge between the version of `stripe/sync-engine` that can be installed via the studio, and the docker image that can be setup for local development. https://github.com/stripe/sync-engine/issues/324 This makes it difficult to use ## To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Install the sync engine via the studio on hosted supabase 2. Setup local supabase dev environment 3. Run the `stripe/sync-engine` docker 4. See it fail due to schema mismatches ## Expected behavior - show in the ui what version of `stripe/sync-engine` is being installed via the dashboard - being able to pin that version somehow, perhaps in the `config.toml` so development and staging branches dont diverge