[Feature Request] Manage migrations to `n` databases

[golanglemonade]

Tenant databases need to have their database schema up to date with the main datum database. We recently moved to goose migrations, which runs the migrations on the container startup of the datum service; We have a few options to keep those up to date - either doing a similar thing across all database connections; or using the parent schema functionality within turso

[golanglemonade]

We are no longer targeting Turso/sqlite for our main database. Instead we need to confirm this with Postgres