Migrations for schema changes #2297

I've noticed that there have been a few recent schema changes (#1963 #2071 #2125 #2128) that modified the existing tables' CREATE statements in the migration files. This leads to these changes not being applied onto Clickhouse instances where the tables already exist.

Is this intended behaviour? It seems difficult for us to detect these missed changes, which could be problematic later if there are new migration files that require those changes to already be made, as those migrations would then fail and the container would crashloop.