fix(workspace): drop the strict =0.1.0 pin on fai-module-sdk-macros

The previous commit (eb7a1d5) bumped the workspace version to
0.1.1 but kept the SDK's dep on the macros crate pinned at
exactly 0.1.0. Result: cargo refused to resolve a workspace
build because the path-resolved macros crate was 0.1.1 while
the dep required =0.1.0. The Cargo.lock from that commit
landed unchanged from the pre-bump state, masking the
breakage in CI artifacts but failing on a fresh build.

Drop the strict pin and use path-only resolution for now,
matching the convention used by tokio/tokio-macros and similar
workspace pairings. The two crates will still move in lockstep
because they share a workspace.package version line.

Bumps the workspace patch version 0.1.1 -> 0.1.2 per the
per-commit policy.

Signed-off-by: flemming-it <sf@flemming.it>

Cargo.lock

@@ -78,7 +78,7 @@ checksum = "877a4ace8713b0bcf2a4e7eec82529c029f1d0619886d18145fea96c3ffe5c0f"
 
 [[package]]
 name = "fai-module-sdk"
-version = "0.1.0"
+version = "0.1.2"
 dependencies = [
  "fai-module-sdk-macros",
  "serde",
@@ -90,7 +90,7 @@ dependencies = [
 
 [[package]]
 name = "fai-module-sdk-macros"
-version = "0.1.0"
+version = "0.1.2"
 dependencies = [
  "proc-macro2",
  "quote",

Cargo.toml

@@ -6,7 +6,7 @@ members = [
 ]
 
 [workspace.package]
-version = "0.1.1"
+version = "0.1.2"
 edition = "2024"
 authors = ["Dr. Stefan Flemming <platform@flemming.ai>"]
 license = "Apache-2.0"

crates/fai-module-sdk/Cargo.toml

@@ -10,7 +10,7 @@ rust-version.workspace = true
 description = "Stable, ergonomic surface for writing F∆I Platform modules in Rust"
 
 [dependencies]
-fai-module-sdk-macros = { path = "../fai-module-sdk-macros", version = "=0.1.0" }
+fai-module-sdk-macros = { path = "../fai-module-sdk-macros" }
 serde = { workspace = true }
 serde_json = { workspace = true }
 thiserror = { workspace = true }