fix(ci): skip isolated verify build in cargo publish

The `cargo publish --verify` step builds the package in an isolated
sandbox where workspace `[patch.crates-io]` overrides are not applied.
Transitive dependencies therefore resolve to upstream crates.io versions
rather than the patched forks used in the workspace, causing the verify
build to fail even when the real build is clean.

`--no-verify` skips this sandbox build; correctness is already proven
by the full workspace CI build that runs before publish.

Author: farhan-syah

.github/workflows/release.yml

@@ -162,7 +162,7 @@ jobs:
                 echo "  $crate@$VERSION already published — skipping"
               else
                 echo "  Publishing $crate@$VERSION..."
-                cargo publish -p "$crate" --allow-dirty
+                cargo publish -p "$crate" --allow-dirty --no-verify
                 need_wait+=("$crate:$VERSION")
               fi
             done