Random question about the schema migrator - are the changes designed to be backwards compatible?
i.e. take the 0.50 -> 0.51 upgrade, we have container changes for frontend and queryservice (0.50.0 ->
0.51.0) as well as otel-collector and schema-migrator (0.102.2 -> 0.102.3).
IF i run in the schema change -> collector -> then query and ui - will the UI and Query Service break after the schema change - i.e. i need downtime for each release. Or does your release process mitigate risks there?