ci: add tag-triggered release workflow for ts and rust crates

[iduartgomez]

Summary

• Add .github/workflows/release.yml that publishes on tag push:
  • typescript-v* → npm publish @freenetorg/freenet-stdlib
  • rust-v* → cargo publish freenet-stdlib
  • rust-macros-v* → cargo publish freenet-macros
• Each job verifies the tag version matches the manifest (package.json or Cargo.toml), runs tests, does a dry-run publish, then the real publish.
• Also supports workflow_dispatch with a dry_run toggle so we can exercise it without pushing a tag.
• Add release-rust Claude skill mirroring release-typescript so both flows are documented end-to-end.
• Update release-typescript skill to list the CI path as preferred.

Required repo secrets

These do not exist yet and must be added before the workflow can publish:

Secret	Used by	How to get
NPM_TOKEN	ts job	npmjs.com → Access Tokens → "Automation" (bypasses 2FA)
CARGO_REGISTRY_TOKEN	rust jobs	crates.io → Account Settings → API Tokens

Without these, jobs will fail at the publish step.

Test plan

• yaml.safe_load parses release.yml cleanly
• After merge: add secrets, run workflow_dispatch with dry_run=true on each target to verify build/pack/dry-run steps pass
• Next real release: push a tag, confirm the workflow publishes