feat: Add automated crate publishing workflow

A new GitHub Actions workflow named `publish-crate.yml` has been added
to automate the process of publishing the Rust crate to `crates.io`.
This workflow is triggered either when a new release is published on
GitHub or can be manually invoked via `workflow_dispatch`.

The workflow includes a crucial validation step that checks if the
GitHub release tag (e.g., `v1.2.3`) precisely matches the crate's
version (e.g., `1.2.3`) found in `Cargo.toml`, prefixed with 'v'. This
ensures version consistency between the Git tag and the published crate.
It uses `cargo publish --locked` to guarantee that the published crate
is built with the exact dependency versions specified in `Cargo.lock`,
enhancing build reproducibility and stability. The publishing operation
requires the `CARGO_REGISTRY_TOKEN` secret for authentication with
`crates.io`. This automation streamlines the release process, minimizes
potential human errors, and maintains version integrity.

Influence:
1. Manually trigger the "Publish to crates.io" workflow for testing
purposes.
2. Create a GitHub release (e.g., `v1.0.0`) and publish it to verify
automatic workflow invocation.
3. Test with a release tag that matches the `Cargo.toml` version (e.g.,
`v1.0.0` for `version = "1.0.0"`) to ensure successful publishing.
4. Test with a release tag that does NOT match the `Cargo.toml` version
(e.g., `v1.0.1` for `version = "1.0.0"`) to confirm the validation step
correctly fails the workflow.
5. Verify that the crate is successfully published to `crates.io` after
a successful workflow run.
6. Ensure the `CARGO_REGISTRY_TOKEN` repository secret is correctly
configured with a valid token.

feat: 添加自动化 crate 发布工作流

新增了 GitHub Actions 工作流 `publish-crate.yml`，用于自动化

Author: zccrs

.github/workflows/publish-crate.yml

@@ -0,0 +1,49 @@
+name: Publish to crates.io
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: publish-crate
+  cancel-in-progress: false
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+
+      - name: Validate tag matches crate version
+        if: startsWith(github.ref, 'refs/tags/')
+        run: |
+          tag="${GITHUB_REF#refs/tags/}"
+          version=$(cargo metadata --no-deps --format-version 1 |
+            python3 - <<'PY'
+            import json,sys
+            meta=json.load(sys.stdin)
+            print(meta['packages'][0]['version'])
+            PY
+          )
+          if [ "${tag}" != "v${version}" ]; then
+            echo "Tag ${tag} does not match crate version v${version}" >&2
+            exit 1
+          fi
+
+      - name: Publish to crates.io
+        env:
+          CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
+        run: |
+          if [ -z "${CARGO_REGISTRY_TOKEN}" ]; then
+            echo "CARGO_REGISTRY_TOKEN is not set" >&2
+            exit 1
+          fi
+          cargo publish --locked --token "${CARGO_REGISTRY_TOKEN}"