Prepare v0.1.1 release publishing

[fannnzhang]

Summary

• bump the workspace and internal OpenWire dependency versions to 0.1.1
• trigger the publish workflow automatically when a v tag is pushed
• keep manual workflow dispatch for dry-runs and partial publish resume
• document the tag-driven release flow and the need to recreate an existing stale tag
• make the publish helper compatible with Bash 3 empty optional args

Verification

• go run github.com/rhysd/actionlint/cmd/actionlint@latest .github/workflows/publish.yml
• bash -n scripts/publish-crates.sh
• cargo fmt --all --check
• cargo metadata --locked --no-deps
• cargo clippy --workspace --all-targets -- -D warnings
• cargo test --workspace --all-targets
• scripts/publish-crates.sh --dry-run

Release note

After this merges, the existing v0.1.1 tag must point at the merged release commit before publishing. If the pushed tag currently points at an older 0.1.0 commit, delete and recreate it on the release commit or use a new version tag.