ci: make manual release workflow runs always as dry-run

[burmecia]

What kind of change does this PR introduce?

This PR makes the release workflow testable on non-tag branches by adding a manual trigger with a version input, that builds artifacts without publishing to crates.io or GitHub Releases.

What is the current behavior?

The current release workflow is trigged by tagging which makes testing this workflow itself hard.

What is the new behavior?

• Added one input version for manual triggering for this workflow
• Update the release workflow so workflow_dispatch runs are always treated as dry-runs without publishing to crates.io or GitHub Releases.

Additional context

This PR also made a minor fix for the linking issue on arm64 platform in release workflow, this fix replaced ld with lld as the default linker to avoid linking issue like below:

error: linking with `cc` failed
relocation truncated to fit: R_AARCH64_CALL26 against symbol `__aarch64_ldadd8_relax`
collect2: error: ld returned 1 exit status
error: could not compile `wrappers` (lib)

[Copilot]

Pull request overview

This PR updates the GitHub Actions release workflow to be testable without creating tags by adding a manual dry-run trigger that builds/packaging artifacts without publishing, and adds an arm64 linker workaround to reduce release build failures.

Changes:

• Add workflow_dispatch inputs (dry_run, version) to support manual dry-run builds with a configurable fake tag.
• Gate crates.io publishing and GitHub Release creation/asset uploads to only run on push tag events.
• Add arm64-specific linker/toolchain configuration (lld) and use an “effective version” for package naming/versioning.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.