commons: re-pin store-types consumers to 0.2.0

The 0.2.0 bump landed with cortexkit-store and cortexkit-store-postgres
still requiring ^0.1.0, which broke the workspace resolve -- caught by
re-running the suite after the bump rather than trusting the pre-bump
green. Same-workspace consumers re-pin in the same change as the bump.

Author: ualtinok

crates/cortexkit-store-postgres/Cargo.toml

@@ -8,7 +8,7 @@ authors.workspace = true
 description = "Postgres backend mechanics (open, native single-writer lease, versioned migrations) for CortexKit module storage."
 
 [dependencies]
-cortexkit-store-types = { version = "0.1.0", path = "../cortexkit-store-types" }
+cortexkit-store-types = { version = "0.2.0", path = "../cortexkit-store-types" }
 cortexkit-lease = { version = "0.1.0", path = "../cortexkit-lease" }
 # Synchronous blocking driver: the store API is synchronous, so the blocking
 # client avoids an async-runtime bridge and confines postgres types to this crate.

crates/cortexkit-store/Cargo.toml

@@ -12,6 +12,6 @@ default = ["sqlite"]
 sqlite = ["dep:rusqlite"]
 
 [dependencies]
-cortexkit-store-types = { version = "0.1.0", path = "../cortexkit-store-types" }
+cortexkit-store-types = { version = "0.2.0", path = "../cortexkit-store-types" }
 cortexkit-lease = { version = "0.1.0", path = "../cortexkit-lease" }
 rusqlite = { version = "0.32", features = ["bundled"], optional = true }