Identify crates.io release requests

[shps951023]

Summary

• send a repository-specific User-Agent with crates.io API requests
• fix HTTP 403 responses in the release preflight and post-publish checks
• preserve the existing v0.5.0 tag and retry flow

The repaired v0.5.0 run passed verification and built both release assets, then failed before Trusted Publishing because crates.io rejected curl's default User-Agent with HTTP 403: https://github.com/mini-software/MiniExcel-Rust/actions/runs/34972783462

After this merges, rerun the Release workflow with workflow_dispatch and tag=v0.5.0.

Validation

• crates.io API with the workflow User-Agent returns 200 for miniexcel/0.4.0
• crates.io API with the workflow User-Agent returns 404 for unpublished miniexcel/0.5.0
• both workflow requests use the identified User-Agent
• actionlint .github/workflows/release.yml
• VS Code workflow diagnostics: no errors
• git diff --check

[coderabbitai]

Warning

Review limit reached

Next included review available in 37 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

This review ran on the open-source allowance, not this organization's plan, because the pull request author doesn't have an assigned seat. Waiting won't change this — ask an organization admin to assign them a seat, or add seats in Billing if every seat is already assigned, then retry.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 0cc7e2cb-e200-4769-b471-d4cd31ec3ed7

📥 Commits

Reviewing files that changed from the base of the PR and between 6e166c9 and 9280063.

📒 Files selected for processing (1)

• .github/workflows/release.yml

---

_{Comment @coderabbitai help to get the list of available commands.}