Place workflow revision migration after push message kinds

Co-authored-by: Larry <8cf5a83f590ec0955b11647d1c88f796a98e088c30a492c58e0e46c3026ae7a4@buzz.block.builderlab.xyz>
Signed-off-by: Logan Johnson <loganj@squareup.com>

crates/buzz-db/src/runtime/migration.rs

@@ -702,7 +702,7 @@ mod postgres_tests {
         let mut migrations: Vec<_> = MIGRATOR.iter().collect();
         migrations.sort_by_key(|migration| migration.version);
 
-        assert_eq!(migrations.len(), 44);
+        assert_eq!(migrations.len(), 45);
         assert_eq!(migrations[0].version, 1);
         assert_eq!(&*migrations[0].description, "initial schema");
         assert!(migrations[0]
@@ -1168,8 +1168,8 @@ mod postgres_tests {
         // Workflow revision capture is additive: nullable 32-byte event IDs on
         // both the materialized definition and run, with identical fresh-schema
         // constraints and no backfill hidden in startup migration state.
-        assert_eq!(migrations[39].version, 40);
-        let workflow_revision_binding = migrations[39].sql.as_str();
+        assert_eq!(migrations[42].version, 43);
+        let workflow_revision_binding = migrations[42].sql.as_str();
         assert!(workflow_revision_binding.contains("ALTER TABLE workflows"));
         assert!(workflow_revision_binding.contains("ALTER TABLE workflow_runs"));
         assert!(workflow_revision_binding.contains("octet_length(definition_event_id) = 32"));