Robust checks on realtime tables and supabase migrations

[bitbeckers]

          @bitbeckers is the idea that it then errors if not all tables are in the publication? Or it then creates a migration where we add all missing tables to the realtime publication?

Different approach: wrapper method for subscribing that checks the table being subscribed to against all tables in the realtime publication. That would solve the problem at startup time, so you'd see it before pushing. I think both would be fine, the wrapper method would keep the migrations cleaner.

Originally posted by @Jipperism in #242 (comment)